What problem does it solve? Bug fixes often ship without regression coverage, letting the same defect return later. This Skill enforces a disciplined test-driven workflow that reproduces the bug as a failing test before any production code changes, then verifies the fix makes it pass. ## Core Features & Use Cases - Failing-Test-First Workflow: Guides a seven-step process from understanding the bug through writing the failing test, fixing the code, and rerunning validation. - Pragmatic Skip Logic: Explicitly avoids forcing impractical tests when harness setup, brittle mocks, or slow end-to-end infrastructure would outweigh the value, substituting the closest executable regression check instead. - Evidence-Based Reporting: Requires naming the failing-before test, the passing-after run, and nearby validation performed rather than just reporting the outcome. - Use Case: A user reports that a date parser returns the wrong timezone offset. The Skill writes a focused unit test that fails on the current behavior, applies the minimal fix, and confirms the test passes along with adjacent test suites. ## Quick Start Ask the agent to fix this bug using TDD by writing a failing regression test first, then making the minimal code change to make it pass.