What problem does it solve? Developers often write production code first and bolt tests on afterward, producing tests that pass immediately and prove nothing. This Skill enforces a strict test-first discipline so every behavior is verified by a test that was watched failing before implementation. ## Core Features & Use Cases - Red-Green-Refactor Enforcement: Guides the full cycle of writing a failing test, verifying the failure, writing minimal code to pass, and refactoring while staying green. - Rationalization Detection: Lists common excuses for skipping TDD (such as "too simple to test" or "I'll test after") and explains why each one fails, with red flags that trigger a restart. - Test Quality Rules: A companion reference defines how to write honest tests that name the break they catch, exercise real code instead of mocks, and pass a mutation check. - Use Case: When fixing a bug where an empty email is accepted, write a failing test asserting the rejection error, watch it fail, implement the minimal validation, and confirm the suite passes. ## Quick Start Ask the AI to implement a new feature or bugfix using strict test-driven development with a failing test written and verified first.
