What problem does it solve? Implementation code written before tests often ships without regression coverage, and tests written afterward can pass without proving the intended behavior. This Skill enforces a strict test-first workflow so every behavior change is proven by a failing test before any production code exists. ## Core Features & Use Cases - RED-GREEN-REFACTOR Enforcement: Requires writing one failing test, verifying it fails for the expected reason, writing minimal code to pass, then refactoring while keeping tests green. - Outer and Inner Loops: Drives acceptance-test-level slices from outside the unit boundary, with inner unit-level cycles running until each acceptance test passes. - Rationalization and Red-Flag Detection: Lists common excuses for skipping tests and stop conditions that force restarting a chunk test-first. - Use Case: When fixing a bug in a Workbench implementation plan, write the failing acceptance test for the chunk first, run inner red-green-refactor cycles until it passes, and only then mark the chunk complete. ## Quick Start Use the test-driven-development skill to implement this feature by writing a failing test first, then the minimal code to pass it, then refactoring.
