test-driven-development

What problem does it solve? It prevents test-driven development from being over-applied to routine work by scoping the Red-Green-Refactor cycle to only the behavior seam the user explicitly requests, avoiding unnecessary fixtures, coverage gates, and full-suite runs. ## Core Features & Use Cases - Focused Test-First Loop: Write the smallest failing test, confirm the failure, implement the minimum change, and re-run only that focused test. - Explicit Opt-In Scope: Activates only when the user requests strict TDD or a task contract requires test-first development, leaving configuration, documentation, and generated files untouched. - Use Case: When a task contract says a new validation rule must be developed test-first, use this Skill to write one failing test for that rule, implement the minimal code to pass it, and stop without adding unrelated test infrastructure. ## Quick Start Ask the assistant to use strict test-driven development for the specific behavior you want implemented, naming the exact seam to test first.