Menu
Run the project test suite and return structured TestResult JSON. Used by dev-pipeline build loop and standalone test verification.
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 build phase — implement feature code from a plan spec without modifying tests. One round per invocation; orchestrator loops with run-tests.
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.
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-run-tests |
| description | Run the project test suite and return structured TestResult JSON. Used by dev-pipeline build loop and standalone test verification. |
| disable-model-invocation | true |
Run the full test suite and return structured results.
None required — discover and run the project's test command.
package.json scripts, pytest, go test, etc.).Standard meaning: passed: true only if all tests pass (green).
End with a fenced json block containing TestResult. Schema: schemas.md.
Include every failure with test name, error message, and file when available.
Use subagent_type: shell when launched via Task.