What problem does it solve? Code written before tests often ships with unverified behavior, and tests written after implementation pass immediately without proving they catch real bugs. This Skill enforces a strict test-first workflow so every change is backed by a test that was watched failing before implementation. ## Core Features & Use Cases - Red-Green-Refactor Cycle: Guides writing one failing test, verifying it fails for the right reason, writing minimal code to pass, then refactoring while staying green. - Rationalization Detection: Lists common excuses ("too simple to test", "I'll test after") with counterarguments and red flags that trigger a restart. - Testing Anti-Patterns Reference: Companion guide covering mock-behavior testing, test-only production methods, incomplete mocks, and over-mocking. - Use Case: When fixing a bug where empty emails are accepted, write a failing test asserting the rejection, watch it fail, implement the validation, and confirm the suite passes before committing. ## Quick Start Ask the agent to implement the next feature or bugfix using test-driven development with a failing test written and verified first.
