test-driven-development

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 change is covered 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 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 — name the break each test catches, assert real behavior instead of mocks, and run a mutation check. - Use Case: When fixing a bug where empty emails are accepted, write a failing test asserting the rejection error, watch it fail, implement the minimal validation, and confirm all tests pass. ## Quick Start Use the test-driven-development skill to implement this feature by writing a failing test first, then the minimal code to make it pass.