subagent-driven-development
Use when executing implementation plans with independent tasks in the current session
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
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.
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
dispatching-parallel-agents
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
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
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
executing-plans
Use when you have a written implementation plan to execute in a separate session with review checkpoints
using-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
using-superpowers
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
Brainstorming Ideas Into Designs
Interactive idea refinement using Socratic method to develop fully-formed designs
remembering-conversations
Use when user asks 'how should I...' or 'what's the best approach...' after exploring code, OR when you've tried to solve something and are stuck, OR for unfamiliar workflows, OR when user references past work. Searches conversation history.
linear
Manage Linear issues. Use when asked about tasks, tickets, bugs, or Linear.
Validating Inputs
Check all external inputs for validity - garbage in, nothing out, never garbage out
