tdd
Installation
SKILL.md
Test-Driven Development — Multi-Agent Orchestration
Enforce disciplined RED-GREEN-REFACTOR cycles using separate subagents for test writing and implementation. The core innovation: the Test Writer never sees implementation code, and the Implementer never sees the specification. This prevents the LLM from leaking implementation intent into test design.
When to Use
- User requests TDD, test-first, or red-green-refactor workflow
- User says
/tddwith a feature description or bug report - User wants to add a feature with test coverage enforced from the start
- User wants to fix a bug by first writing a reproducing test
Invocation Modes
| Invocation | Behavior |
|---|---|
/tdd <feature> |
Interactive mode — pause for approval at slices and each RED checkpoint |
/tdd --auto <feature> |
Autonomous mode — run all slices without pausing; stop ONLY on unrecoverable errors |
/tdd --resume |
Resume from .tdd-state.json in project root |
/tdd --dry-run <feature> |
Validation mode — runs Phase 0 + Phase 1 fully, renders all prompts, but skips Task() calls. No code is written. |