test-driven-development
Test-Driven Development (TDD)
Overview
Write the test first. Watch it fail. Write minimal code to pass.
Core principle: If you didn't watch the test fail, you don't know if it tests the right thing.
Violating the letter of the rules is violating the spirit of the rules.
When to Use
Always:
- New features
- Bug fixes
- Refactoring
- Behavior changes
More from pcvelz/superpowers
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
40using-superpowers
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
40writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
37requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
37executing-plans
Use when you have a written implementation plan to execute in a separate session with review checkpoints
36subagent-driven-development
Use when executing implementation plans with independent tasks in the current session
35