What problem does it solve? Developers often write production code first and add tests afterward, which produces tests that may pass for the wrong reasons or fail to verify actual behavior. 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 Cycle: Guides writing one minimal failing test, verifying the failure, implementing the simplest passing code, then refactoring while keeping tests green. - Failure Verification Gates: Mandates watching each test fail for the expected reason (missing feature, not typos) before any production code is written. - Completion Checklist: Provides a verification checklist covering test coverage, minimal implementation, pristine output, and edge cases. - Use Case: When implementing a retry mechanism, write a test asserting the operation retries three times, watch it fail, implement the minimal retry logic, confirm all tests pass, then refactor. ## 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.
