Menu
Use when implementing a high-risk behavior change, reproduced regression, or costly contract. Do NOT use by default for docs, styling, config, or low-risk wiring.
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
Use when a request leaves material product, architecture, behavior, or scope decisions unresolved. Do NOT use for approved, well-bounded implementation work.
Use when 2 or more substantial tasks are independent, have disjoint state, and parallel execution will save meaningful time. Do NOT use for coupled or sequential work.
Use when implementing an approved written plan with dependent tasks in the current session. Do NOT use when the plan is missing, unapproved, or naturally parallel.
Use when verified implementation is ready and the user must choose whether to keep, merge, or publish the branch. Do NOT use before applicable checks pass.
Use when receiving code review feedback that may be unclear or technically questionable and needs verification. Do NOT use for an unrequested general code review.
Use when a completed change is high-risk, crosses subsystem boundaries, or the user explicitly requests independent review. Do NOT use by default for low- or medium-risk changes.
| name | test-driven-development |
| version | 6.2.0 |
| category | workflow |
| description | Use when implementing a high-risk behavior change, reproduced regression, or costly contract. Do NOT use by default for docs, styling, config, or low-risk wiring. |
TDD protects critical behavior. It is not a requirement to create a test for every changed function.
Read ../using-superpowers/references/risk-policy.md and classify the change.
| Risk | New test |
|---|---|
| Low | None by default; use a focused check or smoke path |
| Medium | Only for a key outcome, non-obvious branch, or hard-to-notice regression |
| High | One minimal regression or contract test first when practical |
Do not test private helpers, trivial branches, static rendering details, or behavior already covered through a public seam.
For a warranted test:
Mocks are limited to external boundaries. Prefer real in-process behavior.
Do not delete completed code merely because the test was not written first. Add a focused regression test when it materially protects the outcome. If automation is disproportionately expensive or impossible, record and run a reproducible smoke check instead.
