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 disciplined workflow where a failing test is written before any implementation, so every behavior change carries proof that it works. ## Core Features & Use Cases - Red-Green-Refactor Cycle: Write a failing test first, implement the minimum 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 a fix, guaranteeing the fix actually resolves the issue. - Stack Discovery and Test Quality Guidance: Detect the repository's own test commands and frameworks, and apply practices like the test pyramid, DAMP over DRY, state-based assertions, and preferring real implementations over mocks. - Use Case: A bug report says completing a task does not set its timestamp. Write a test asserting completedAt is set, watch it fail, implement the fix, watch it pass, then run the full suite to confirm no regressions. ## Quick Start Use test-driven development to implement this feature, starting with a failing test before writing any implementation code.