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 workflow so every behavior change is backed by a test that was watched failing before implementation. ## Core Features & Use Cases - Red-Green-Refactor Enforcement: Guides the full TDD cycle with mandatory verification that each test fails for the right reason before any production code is written. - Rationalization Countermeasures: Provides a table of common excuses ("too simple to test", "I'll test after") with rebuttals, plus red flags that trigger a restart of the cycle. - Test Quality Rules: A companion reference defines how to write honest tests: name the break each test catches, assert on real behavior instead of mocks, and run a mutation check before finishing. - 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, verify it passes, then refactor. ## Quick Start Ask the agent to implement a new feature or bugfix using strict test-driven development with a failing test written and verified first.
