What problem does it solve? Developers often write production code before tests, producing tests that pass immediately and prove nothing. 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 full cycle of writing a failing test, verifying the failure, writing minimal passing code, and refactoring safely. - Rationalization Detection: Lists common excuses for skipping TDD and red flags that signal the process was violated, with instructions to delete code and restart. - Subagent Integration: Shows how to embed TDD requirements into delegated tasks and pair with systematic debugging so every bugfix starts with a reproducing test. - Use Case: When asked to add a retry mechanism to an API client, write a failing test asserting three retry attempts, watch it fail, implement the minimal retry logic, verify it passes, then refactor. ## Quick Start Ask the agent to implement the next feature using strict test-driven development with a failing test written and verified before any production code.