obra

using-superpowers

obra

Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

writing-skills

obra

Use when creating new skills, editing existing skills, or verifying skills work before deployment

receiving-code-review

obra

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

using-git-worktrees

obra

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

writing-plans

obra

Use when you have a spec or requirements for a multi-step task, before touching code

test-driven-development

obra

Use when implementing any feature or bugfix, before writing implementation code

systematic-debugging

obra

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

subagent-driven-development

obra

Use when executing implementation plans with independent tasks in the current session

requesting-code-review

obra

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

executing-plans

obra

Use when you have a written implementation plan to execute in a separate session with review checkpoints

dispatching-parallel-agents

obra

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

brainstorming

obra

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.