What problem does it solve?
This Skill solves the widespread issue of shipping untested, buggy production code that causes outages, regressions, and hours of unplanned debugging by enforcing a strict test-first development workflow.
Core Features & Use Cases
- Strict TDD Cycle Enforcement: Guides you through the Red (write failing test), Green (minimal implementation), Refactor workflow to ensure every feature, bug fix, or behavior change is test-validated before any production code is written.
- Testing Anti-Pattern Prevention: Includes reference guidance to avoid common testing mistakes like testing mock behavior, adding test-only methods to production code, and creating incomplete mocks.
- Use Case: When fixing a bug where empty email addresses are accepted in a user registration form, this Skill ensures you write a failing test for the empty email case before modifying any implementation code, preventing similar regressions in the future.
Quick Start
Use the test-driven-development skill to build the new user notification feature by first writing a failing test for unsubscribed user handling before writing any production code.