What problem does it solve? Developers often write production code first and bolt tests on afterward, which produces tests that pass immediately and prove nothing about correctness. This Skill enforces a strict test-first discipline so every behavior change is verified 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 while staying green. - Rationalization Countermeasures: Provides a catalog of common excuses for skipping TDD (e.g., "too simple to test", "I'll test after") with concrete rebuttals and red flags that trigger a restart. - Test Quality Rules: The bundled writing-good-tests.md reference defines how to name the break each test catches, derive expectations independently, and mock at the right level. - Use Case: When fixing a bug where an empty email is accepted, write a failing test asserting the rejection error, watch it fail, implement the minimal validation, and confirm the suite passes. ## Quick Start Ask the assistant to implement a new feature or bugfix using strict test-driven development with a failing test written first.
