What problem does it solve? Writing tests after implementation often produces tests that merely confirm existing behavior rather than verify desired behavior, leaving gaps that let real bugs slip through. This Skill enforces a disciplined test-first workflow so every feature and bug fix is backed by a failing test before any code is written. ## Core Features & Use Cases - RED/GREEN/REFACTOR Cycle: Structured phases with concrete rules for writing failing tests, minimal implementations, and safe refactoring, each cycle lasting 5-15 minutes. - Evidence Capture & Git Checkpoints: Templates for documenting each phase and commit conventions (test/feat/refactor) at every transition so you can revert to known-good states. - Mutation Testing: Integrates Stryker to verify tests actually catch bugs, targeting a mutation score above 80% to expose test gaps. - Use Case: When fixing a bug in a pricing module, write a regression test that reproduces the failure first, watch it fail, implement the minimal fix, then refactor while keeping all tests green. ## Quick Start Use the tdd-workflow skill to implement a calculateDiscount function test-first with the RED/GREEN/REFACTOR cycle.