Menu
TDD build phase — implement feature code from a plan spec without modifying tests. One round per invocation; orchestrator loops with run-tests.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
TDD phase 5 — commit if tests pass and review confidence >= 7, write result.md summary. Used by dev-pipeline orchestrator.
TDD phase 2 — run the test suite and confirm correct red state (tests fail before implementation). Used by dev-pipeline orchestrator after write-tests.
TDD phase 4 — adversarial review of implementation against the plan spec. Returns confidence score 0-10. Used by dev-pipeline orchestrator.
Run the project test suite and return structured TestResult JSON. Used by dev-pipeline build loop and standalone test verification.
Orchestrates the TDD build pipeline: read plan → write tests → red check → build until green → review → commit. Launches phase subagents via Task. Use when building from plans/<feature>/plan.md, running dev-pipeline, or implementing a spec after dev-plan.
TDD phase 1 — write the full test suite from a plan spec before any implementation exists. Used by dev-pipeline orchestrator or standalone when writing tests from plans/*/plan.md Test contracts.
| name | dev-pipeline-implement |
| description | TDD build phase — implement feature code from a plan spec without modifying tests. One round per invocation; orchestrator loops with run-tests. |
| disable-model-invocation | true |
Implement the feature described in the plan. One build round — do not run the full test suite (orchestrator invokes run-tests next).
plans/<feature>/plan.md (required)specPath fully before writing code.round > 1, prioritize fixing failures listed in previousFailures.round === 1, implement from scratch per the spec.Report:
Do not return TestResult JSON — run-tests handles verification.