/writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
obra/superpowers
An agentic skills framework & software development methodology that works.
Repository statistics
Indexed skills
15
Skill groups
1
GitHub stars
0
Forks
0
Skills
15 total/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.
/diagnosing-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.
/executing-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
/requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
/subagent-driven-development
Use when executing implementation plans with independent tasks in the current session
/test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
/using-superpowers
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
/writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
/finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work
/receiving-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
/using-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
/verification-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
/systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
/dispatching-parallel-agents
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
GitHub repository metadata loaded, but the SKILL.md file scan is unavailable right now.
Add to your README
The badge links readers to this page. It shows the skilld mark and no counts, and it follows the reader's light or dark GitHub theme.
<a href="https://skilld.dev/gh/obra/superpowers">
<picture>
<source media="(prefers-color-scheme: dark)" srcset="https://skilld.dev/b/obra/superpowers?theme=dark">
<source media="(prefers-color-scheme: light)" srcset="https://skilld.dev/b/obra/superpowers?theme=light">
<img alt="Skill repository on skilld.dev" src="https://skilld.dev/b/obra/superpowers?theme=light">
</picture>
</a>