# skills by Jesse Vincent
Receiving Code ReviewUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical…Requesting Code ReviewUse when completing tasks, implementing major features, or before merging to verify work meets requirements.Writing PlansUse when you have a spec or requirements for a multi-step task, before touching code.Test Driven DevelopmentUse when implementing any feature or bugfix, before writing implementation code.BrainstormingYou MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior.Systematic DebuggingUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes.Finishing A Development BranchUse when implementation is complete, all tests pass, and you need to decide how to integrate the work.Using Git WorktreesUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via…Writing SkillsUse when creating new skills, editing existing skills, or verifying skills work before deployment.Dispatching Parallel AgentsUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies.Subagent Driven DevelopmentUse when executing implementation plans with independent tasks in the current session.Executing PlansUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution.Using SuperpowersUse when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions.Verification Before CompletionUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output…
