What problem does it solve? Code written before tests often ships untested or with tests that pass immediately and prove nothing. This Skill enforces a strict test-first discipline so every behavior change is backed by a test that was watched failing before implementation. ## Core Features & Use Cases - Red-Green-Refactor Enforcement: Mandates writing a failing test first, verifying it fails for the right reason, then writing minimal code to pass. - Rationalization Detection: Lists common excuses for skipping TDD ("too simple to test", "I'll test after") with concrete rebuttals and red flags that trigger a restart. - Test Quality Rules: A companion reference defines how to write honest tests — naming the break each test catches, avoiding mock assertions, and running a mutation check. - Use Case: When fixing a bug where empty emails are accepted, write a failing test asserting the rejection, watch it fail, implement the minimal validation, and confirm the suite stays green. ## Quick Start Ask the agent to implement your next feature or bugfix using strict test-driven development with a failing test written first.
