What problem does it solve? Code changes made without tests often introduce regressions and unverified behavior. This Skill enforces a disciplined test-driven development workflow so every feature, bug fix, or refactor is backed by a focused failing test before implementation begins. ## Core Features & Use Cases - Test-First Workflow: Guides writing or updating a narrow failing test before touching production code, then implementing the smallest change to make it pass. - Verification Discipline: Runs the narrowest relevant tests plus lint, typecheck, or static analysis, broadening coverage when shared behavior or public APIs change. - Pragmatic Exceptions: Defines clear rules for when test-first is impractical, such as mechanical changes, CSS-only updates, or missing test frameworks, while still requiring nearby coverage. - Use Case: When asked to fix a bug in a payment calculation, the Skill first adds a regression test reproducing the bug, confirms it fails, implements the minimal fix, and reports all verification commands and results. ## Quick Start Use the tdd-development skill to implement this feature by writing a failing test first and verifying it passes.
