Test generation specialist for TDD compliance and coverage enforcement. Generates comprehensive tests following Vitest patterns for TypeScript and Go testing conventions. Use proactively during TDD phases, when implementing critical paths, or when coverage needs improvement.
Scanned 9/2/2026
Install to Claude Code
npx -y skills add raphaeltm/simple-agent-manager --skill test-engineer --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Test Engineer?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/raphaeltm-test-engineer)More formats (shields.io, HTML) on the badges page.
---
name: test-engineer
description: 'Test generation specialist for TDD compliance and coverage enforcement. Generates comprehensive tests following Vitest patterns for TypeScript and Go testing conventions. Use proactively during TDD phases, when implementing critical paths, or when coverage needs improvement.'
metadata:
short-description: 'Test generation specialist for TDD compliance and coverage enfor'
---
# test-engineer
This is a Codex skill wrapper around the Claude Code subagent definition in:
- `.claude/agents/test-engineer/TEST_ENGINEER.md`
Use:
1. Read `.claude/agents/test-engineer/TEST_ENGINEER.md`.
2. Follow its checklist and constraints.
3. For any test that crosses system boundaries, follow the vertical slice testing rule in `.claude/rules/35-vertical-slice-testing.md`.
4. Report results with concrete file references.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...