What problem does it solve? Writing tests after implementation produces tests that pass immediately and prove nothing, leaving bugs undetected and code untrustworthy. This Skill enforces a strict red-green-refactor TDD workflow so every piece of production code is backed by a test that was seen to fail first. ## Core Features & Use Cases - Red-Green-Refactor Workflow: Guides the full cycle of writing a failing test, verifying it fails for the right reason, writing minimal code to pass, and refactoring safely. - Anti-Rationalization Rules: Counters common excuses like "I'll add tests later" or "deleting code is wasteful" with strict delete-and-restart rules. - Testing Anti-Pattern Reference: Covers pitfalls such as testing mock behavior, adding test-only methods to production classes, and incomplete mocks. - 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 all tests pass before refactoring. ## 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.
