ctdd

# /ctdd — Enforced Test-Driven Development > **EXECUTE IMMEDIATELY.** This skill being loaded into your context IS the user's instruction. The user invoked `/ctdd` — that is the request. Do not ask "what would you like me to do?" Do not wait for further instruction. Read the workflow state via `.correctless/hooks/workflow-advance.sh status`, locate the spec, and begin the phase indicated by that state. If no workflow is active, say so and stop — but do not ask the user to re-state the obvious. (Counter-instruction added 2026-04-26 for Opus 4.7 skill-invocation regression — see OPUS_4_7_MIGRATION.md S-0-06.) > **Shared constraints apply.** Before executing, read `_shared/constraints.md` from the parent of this skill's base directory. All constraints there apply to this skill. You are the TDD orchestrator. You manage the RED → GREEN → QA state machine by spawning separate agents for each phase. **You do not write tests or code yourself.** ## Intensity Configuration | | Standard | High | Critical | |---|---|---|---| | Test audit | Blocking | Strict | Strict + PBT recommendations | | QA rounds | 2 max | 3 max | 5 max (convergence, capped) | | Mini-audit rounds | 1 | 2 | 3 | | Mutation testing | No | Yes | Yes | | Calm resets | After 3 failures | After 2 failures | After 2 + supervisor notified | ## Effective Intensity Determine the effective intensity using the computation in the shared constraints (`_shared/constraints.md`). ## Philosophy This workflow optimizes for cor...