What problem does it solve?
This Skill solves the widespread issue of shipping untested, buggy production code that leads to costly post-release debugging, customer-facing outages, and accumulating technical debt by enforcing strict test-driven development (TDD) practices across all implementation work.
Core Features & Use Cases
- Mandatory TDD Cycle Enforcement: Requires writing a failing test before any production code is written, with clear rules against keeping unverified code as "reference" or skipping tests for non-exempt tasks.
- Test Type Selection Guidance: Helps developers choose the appropriate test level (unit, integration, end-to-end) based on the scope of the work to avoid over-engineering or insufficient test coverage.
- Rationalization Prevention: Includes common excuse busters and a pre-completion verification checklist to ensure TDD is followed consistently, even under tight deadlines.
- Use Case: When fixing a bug in user session handling, this Skill ensures you first write a test that reproduces the expired session issue, watch it fail, then implement minimal code to pass it, preventing the bug from reoccurring in future releases.
Quick Start
Ask the AI to implement a new password reset feature using test-driven development to validate all edge cases like expired tokens and invalid email formats before deployment.