brainstormingUse before any creative work — creating features, building components, adding functionality, or modifying behavior. Explores intent, requirements and design before implementation.
dispatching-parallel-agentsUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
executing-plansUse when executing an implementation plan yourself in the current session — your human partner chose inline execution, or no subagent tool is available
finishing-a-development-branchUse when implementation is complete, all tests pass, and you need to integrate work
receiving-code-reviewUse when receiving code review feedback — requires technical rigor and verification, not performative agreement
requesting-code-reviewUse when completing tasks, implementing features, or before merging to verify work
subagent-driven-developmentUse when executing implementation plans with independent tasks in the current session
systematic-debuggingUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes
test-driven-developmentUse when implementing any feature or bugfix, before writing implementation code
using-git-worktreesUse when starting feature work that needs isolation from current workspace or before executing plans
using-proctorUse when starting any conversation — establishes skill discovery, enforcement hooks, and the rule that skills precede action
verification-before-completionUse when about to claim work is complete, fixed, or passing — evidence before assertions always
writing-plansUse when you have a spec or requirements for a multi-step task, before touching code
writing-skillsUse when creating new skills, editing existing skills, or verifying skills work before deployment