tdd-disciplinelisted

# TDD Discipline — Iron Law + Cycle Evidence > **SUBAGENT-STOP gate**: if you are running as a subagent invoked by another subagent, STOP. Return `status: blocked` with reason `nested-subagent-loop-detected`. TDD discipline must be applied at the implementer level, not recursively. > **Principios destilados** (obra/Superpowers Iron Law + Gentleman/gentle-ai Cycle Evidence + nuestro return envelope): la disciplina TDD requiere reglas explícitas, anti-rationalization activa y evidencia estructurada en el output. No basta con afirmar "tests pasan". ## The Iron Law (7 rules) 1. **NEVER modify a test to make it pass** — fix the implementation instead 2. **WRITE THE TEST FIRST** (red phase) when the task requires a new test 3. **Confirm the test fails for the EXPECTED REASON** before implementing 4. Implement minimal code to pass (green phase) 5. Refactor only after green 6. If a pre-existing test fails after your change, the implementation is wrong — do NOT touch the test 7. If no failing test exists and task requires one → `status: blocked` ## Anti-rationalization table Reject these excuses immediately: | Excuse | Reality | |-------------------------------------------------|---------------------------------------------------| | "The test was wrong" | Fix the spec, then the test, then the impl | | "It's just a small adjustment to the assert" | That IS modif