tddlisted

# TDD — Test-Driven Development ## Iron Law NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST. Violating the letter of this process is violating the spirit of this process. ## Process ### Red → Green → Refactor 1. **Red**: Write a failing test that describes the desired behavior - Test name should read like a spec: `it("returns 401 when token is expired")` (reason: the test name IS your specification — it must communicate intent to future readers) - Run the test — confirm it fails for the right reason (reason: a test that fails for the wrong reason gives false confidence) 2. **Green**: Write the minimum code to make the test pass - Do not write more than needed — because premature optimization is the root of all evil; make it work first - Do not optimize yet — because optimization without a passing test is speculation, not engineering - Run the test — confirm it passes (reason: a passing test is the only proof the code works) 3. **Refactor**: Clean up without changing behavior - Extract duplicates, rename for clarity, simplify — because readability matters more than cleverness - Run tests again — must still pass (reason: refactoring without re-running tests is just renaming bugs) ### Cycle Repeat for each behavior. One test, one behavior, one cycle — because scope creep in a single test cycle leads to unverified code. ## When to Trigger - `/go` subagents: always — because autonomous agents without TDD produce unverified code - New function or metho