Test-Driven Development (Spec Kit Plus)

What problem does it solve?

It prevents incomplete or fragile implementations by enforcing that you verify requirements through a failing test before writing production code, reducing regressions and debugging churn.

Core Features & Use Cases

• Iron Law: failing test first: Requires starting with a test that demonstrates the feature is missing or the bug reproduces before changing production behavior.
• Tight TDD loop (Red → Green → Refactor): Guides you to implement the minimum code to pass, then refactor without introducing new behavior.
• Workflow alignment with sp- tasks*: Applies specifically when working in sp-implement, sp-debug, sp-fast, and sp-quick so your first step is evidence-based and requirement-complete.

Quick Start

Use the test-driven-development skill when you begin a change to ensure you first write a failing test that proves what is currently broken or missing, then write the smallest production code change to make it pass.