Superpowers · Software Development
Guide coding agents through design, planning, implementation, debugging, and review with reusable development Skills.
Superpowers provides 15 composable Skills for software development. This collection includes the repository's complete Skills directory, with its supporting files and cross-Skill references. Tool-specific plugin hooks and integrations remain part of the upstream project.
Use cases
- Designing and implementing features
- Debugging and verifying fixes
- Planning work and reviewing changes
How to use
Start by clarifying requirements with brainstorming, then plan the work and choose inline or subagent implementation. Use testing, debugging, and review Skills as needed. For the official tool-specific plugin setup, follow the source repository's installation guide.
Skills
brainstorming
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.
obra/superpowersdiagnosing-superpowers
Use 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.
obra/superpowersdispatching-parallel-agents
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
obra/superpowersexecuting-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
obra/superpowersfinishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work
obra/superpowersreceiving-code-review
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
obra/superpowersrequesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
obra/superpowerssubagent-driven-development
Use when executing implementation plans with independent tasks in the current session
obra/superpowerssystematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
obra/superpowerstest-driven-development
Use when implementing any feature or bugfix, before writing implementation code
obra/superpowersusing-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback
obra/superpowersusing-superpowers
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
obra/superpowersverification-before-completion
Use 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
obra/superpowerswriting-plans
Use when you have a spec or requirements for a multi-step task, before touching code
obra/superpowerswriting-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
obra/superpowers