What problem does it solve?
This Skill eliminates the risk of unreliable, regression-prone code that comes from writing production logic before tests, which leads to hard-to-debug failures and accumulating technical debt that slows down future development.
Core Features & Use Cases
- Strict TDD Cycle Enforcement: Mandates the RED-GREEN-REFACTOR workflow for all feature implementation, bug fixes, and refactoring tasks, with mandatory verification of test failure before any production code is written.
- Anti-Pattern Guardrails: Provides explicit rules and examples to avoid common testing mistakes like validating mock behavior instead of real code, adding test-only methods to production classes, and writing tests after implementation.
- Use Case: When building a new user notification system, use this Skill to write failing tests for edge cases like empty recipient lists first, then implement the minimal code to pass those tests, ensuring no edge cases are missed and future changes to the notification logic won't break existing functionality.
Quick Start
Use the test-driven-development skill to implement the new payment processing validation feature by first writing a failing test for the invalid card number detection logic before writing any production code.
