tdd-hybridlisted

# Test-Driven Development (Hybrid Edition) ## Overview **Core principle:** Tests verify behavior through public interfaces, not implementation. If you didn't watch the test fail, you don't know if it tests the right thing. **Hybrid approach:** Superpowers discipline (Iron Law, Delete means delete) + MattPocock intelligence (Planning, Domain awareness, Vertical slicing). --- ## Scope Triage Before starting, classify the work: | Signal | Voie | Pipeline | |--------|------|----------| | Bug fix isolé OU fonction simple <20 lignes OU <3 behaviors | **LIGHT** | Skip Planning → Tracer Bullet → Loop | | Feature ≥3 behaviors OU touche architecture OU nouveau module | **FULL** | Planning → Tracer Bullet → Loop → Refactor avancé | **LIGHT:** 1 question ("Behaviors à tester ?"), discipline stricte, refactor basique **FULL:** Planning complet, domain awareness, deep modules En cas de doute → LIGHT, puis upgrade to FULL si complexité émerge. --- ## The Iron Law ``` NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST ``` Write code before the test? **Delete it. Start over.** **No exceptions:** - Don't keep it as "reference" - Don't "adapt" it while writing tests - Don't look at it - Delete means delete Thinking "skip TDD just this once"? Stop. That's rationalization. --- ## Anti-Pattern: Horizontal Slices **DO NOT write all tests first, then all implementation.** This is "horizontal slicing" — treating RED as "write all tests" and GREEN as "write all code." This produces