executing-plans
Use when you have a written implementation plan to execute in a separate session with review checkpoints
dispatching-parallel-agents
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
parallel-exploration
Use when you need parallel, read-only exploration with task() (Scout fan-out)
code-reviewer
Use when reviewing implementation changes against an approved plan or task (especially before merging or between Hive tasks) to catch missing requirements, YAGNI, dead code, and risky patterns
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
brainstorming
Use before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.