skill-tdd

# Test-Driven Development (TDD) ## MANDATORY COMPLIANCE — DO NOT SKIP **When this skill is invoked, you MUST run the TDD pipeline through `orchestrate.sh` (red → green → refactor) with real provider dispatch. You are PROHIBITED from:** - Writing implementation before a failing test exists - Simulating provider output instead of dispatching via `orchestrate.sh` - Declaring the task "too small for TDD" and skipping the cycle without asking the user - Marking work complete while any test is red or skipped - Rationalizing that a direct edit is faster — the user invoked TDD for test-first discipline ## The Iron Law <HARD-GATE> NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST </HARD-GATE> **Violating the letter of this rule is violating the spirit of this rule.** Write code before the test? **Delete it. Start over.** - Don't keep it as "reference" - Don't "adapt" it while writing tests - Don't look at it - Delete means delete ## Red-Green-Refactor Cycle ``` ┌─────────┐ │ RED │ ← Write ONE failing test └────┬────┘ ↓ ┌─────────┐ │ VERIFY │ ← Watch it FAIL (mandatory) └────┬────┘ ↓ ┌─────────┐ │ GREEN │ ← Write MINIMAL code to pass └────┬────┘ ↓ ┌─────────┐ │ VERIFY │ ← Watch it PASS (mandatory) └────┬────┘ ↓ ┌─────────┐ │REFACTOR │ ← Clean up (stay green) └────┬────┘ ↓ [REPEAT] ``` ## Phase 1: RED - Write Failing Test Write ONE minimal test showing what should happen. **Good ...