What problem does it solve? Developers often write production code first and add tests afterward, which produces tests that pass immediately and prove nothing about correctness. This Skill enforces a strict test-first discipline so every feature and bugfix is backed by a test that was watched failing before implementation. ## Core Features & Use Cases - Red-Green-Refactor Enforcement: Guides the AI to write one minimal failing test, verify it fails for the right reason, implement minimal code to pass, then refactor while staying green. - Rationalization Detection: Lists common excuses for skipping TDD ("too simple to test", "I'll test after") with concrete rebuttals, plus red flags that trigger a restart. - Testing Anti-Pattern Reference: A companion reference covers testing mock behavior, test-only methods in production classes, incomplete mocks, and mocking without understanding dependencies. - Use Case: When asked to fix a bug where an empty email is accepted, the Skill first writes a failing test asserting the rejection, watches it fail, then implements the minimal validation fix. ## 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.
