Software development methodology built on composable skills: the agent clarifies the spec, writes a plan, then executes with TDD and subagent-driven development.
Install
npx skills add obra/superpowersgh skill install obra/superpowersgit clone --depth 1 https://github.com/obra/superpowersSkills in this collection
- BrainstormingobraYou MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
- Diagnosing SuperpowersobraUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.
- Dispatching Parallel AgentsobraUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
- Executing PlansobraUse when you have a written implementation plan to execute in a separate session with review checkpoints
- Finishing A Development BranchobraUse 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
- Receiving Code ReviewobraUse 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
- Requesting Code ReviewobraUse when completing tasks, implementing major features, or before merging to verify work meets requirements
- Subagent Driven DevelopmentobraUse when executing implementation plans with independent tasks in the current session
- Systematic DebuggingobraUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes
- Test Driven DevelopmentobraUse when implementing any feature or bugfix, before writing implementation code
- Using Git WorktreesobraUse 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 SuperpowersobraUse when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
- Verification Before CompletionobraUse 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
- Writing PlansobraUse when you have a spec or requirements for a multi-step task, before touching code
- Writing SkillsobraUse when creating new skills, editing existing skills, or verifying skills work before deployment