Tdd

Forces you to write tests before code, then implements just enough to pass them. The workflow runs plan-agent to design test cases, arbiter to write failing tests, kraken to implement minimal code, then arbiter again to validate. It's strict about the red-green-refactor cycle with no exceptions allowed. The philosophy guide is uncompromising: if you wrote code before watching a test fail, delete it and start over. Best for features where you need coverage guarantees or want to avoid debugging sessions later. The "delete means delete" stance and table of rationalizations are blunt but useful if you keep cutting corners on TDD discipline.