using-superpowers
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
Before you install
- Last update
- Files in folder
- 8
- Scripts
- No script files found
- SKILL.md size
- 3.1 KB (about 798 tokens of context each time it loads)
- License
- MIT
- Source on GitHub
- obra/superpowers
Skills are plain text instructions the agent follows, sometimes with scripts. Check the source, prefer repositories with many installs and stars, and read any script it ships.
Install
npx skills add obra/superpowers@using-superpowersRuns in a terminal with Node.js 18 or newer. Add -y to skip the prompts and -g to install for every project instead of this one.
Install for your agent
npx skills add obra/superpowers@using-superpowers --agent claude-code -y- Project install writes to
.claude/skills/using-superpowers- Global install writes to
~/.claude/skills/using-superpowers
Start a new session afterwards so the agent picks the skill up. In Claude Code you can also call it directly with /using-superpowers.
What it does
If you were dispatched as a subagent to execute a specific task, ignore this skill. If you think there is even a 1% chance a skill might apply to what you are doing, you ABSOLUTELY MUST invoke the skill. IF A SKILL APPLIES TO YOUR TASK, YOU DO NOT HAVE A CHOICE. YOU MUST USE IT. This is not negotiable. You cannot rationalize your way out of this. The Rule Invoke relevant or requested skills BEFORE any response or action — including clarifying questions, exploring the codebase, or checking files. If it turns out wrong for the situation, you don't have to use it. Before entering plan mode: if…
Excerpt from the skill's own SKILL.md. Read the full file on GitHub before installing: skills run with your agent's permissions.
Related skills
- brainstorming
obra/superpowers
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).
- systematic-debugging
obra/superpowers
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
- writing-plans
obra/superpowers
Use when you have a spec or requirements for a multi-step task, before touching code
- requesting-code-review
obra/superpowers
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
- verification-before-completion
obra/superpowers
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
- executing-plans
obra/superpowers
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