Menu
Use when the user wants regression-first or test-first scaffolding before implementation work expands.
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 the user wants architecture-first product and system design with explicit stack rationale, boundaries, tradeoffs, data model choices, and phased delivery planning.
Use when the user wants to decide whether implementation is ready, what remains blocked, and what the exact next build step should be.
Use when the user wants logic validation: states, transitions, invariants, edge cases, dead ends, and blockers before implementation.
Use when the user wants evidence-backed technology choices, OSS evaluation, and source-grounded validation of the stack proposed in `$arch`.
Use when the user wants a security and trust-boundary review of the current design before implementation or release.
Use when the user wants a DX and UX review of the planned workflow before implementation proceeds.
| name | tdd |
| description | Use when the user wants regression-first or test-first scaffolding before implementation work expands. |
Use this skill inside Codex when implementation should start by locking behavior with tests. tdd is a non-gating helper skill that supports execution once the relevant lane is ready.
Produce:
$cleanuptdd as a replacement for the build gate.