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 abudhahir/superpowers
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
11writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
8brainstorming
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.
8writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
8executing-plans
Use when you have a written implementation plan to execute in a separate session with review checkpoints
8using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
8