What problem does it solve? Code changes made without tests ship unverified behavior, and bug fixes without reproduction tests leave regressions unguarded. This Skill enforces a write-the-failing-test-first workflow so every behavior change is proven by an automated test. ## Core Features & Use Cases - Red-Green-Refactor Loop: Write a failing test, implement the minimal code to pass it, then refactor with tests green. - Prove-It Pattern for Bug Fixes: Reproduce any reported bug with a failing test before attempting the fix, then verify the fix and run the full suite. - Stack Discovery & Test Quality Guidance: Detect the repository's own test runner and conventions, and apply practices like the test pyramid, DAMP over DRY, state-based assertions, and real implementations over mocks. - Use Case: A bug report says completing a task doesn't set its timestamp. Write a failing reproduction test confirming the bug, implement the fix, watch the test pass, then run the full suite to rule out regressions. ## Quick Start Use test-driven development to fix this bug: first write a failing test that reproduces it, then implement the minimal fix and run the repository's full test suite.