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.
Executing Plans
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Subagent Driven Development
Use when executing implementation plans with independent tasks in the current session
Test Driven Development
Use when implementing any feature or bugfix, before writing implementation code
Finishing A Development Branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Systematic Debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Using Superpowers
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
Receiving Code Review
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
Verification Before Completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
Writing Plans
Use when you have a spec or requirements for a multi-step task, before touching code
Writing Skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Dispatching Parallel Agents
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Requesting Code Review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Using Git Worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback