メニュー
TDD phase 2 — run the test suite and confirm correct red state (tests fail before implementation). Used by dev-pipeline orchestrator after write-tests.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
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 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-red-check |
| description | TDD phase 2 — run the test suite and confirm correct red state (tests fail before implementation). Used by dev-pipeline orchestrator after write-tests. |
| disable-model-invocation | true |
Run the test suite. No implementation should exist yet — tests should fail.
Return TestResult JSON where:
passed: true — tests fail as expected (import errors, assertion errors, runtime errors). This is the correct red state.passed: false — tests somehow pass. Tests may be too weak or implementation already existed.List every failing test in failures.
End with a fenced json block containing TestResult. Schema: schemas.md.
Use subagent_type: shell when launched via Task if the subagent only needs to run tests.