using-superpowers
The facts
Its description
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
The description the agent reads to decide when to use it.
When it starts
This is a bootstrap skill: its description says to use it when starting any conversation, and the Muse reference notes it is injected automatically at SessionStart by the plugin hook, so it is loaded by the harness rather than by anything a person says. Its job is to make the agent invoke relevant skills before any response, including clarifying questions.
A model's summary of when it is used.
Who can start it
A hook loads it
A hook loads it by itself, with no request from you.
Starts other agents
3 lines mention starting other agents
Lines in the file that mention starting another agent. Found by matching words, so treat them as pointers.
Files it mentions
references/claude-code-tools.md, references/codex-tools.md, references/pi-tools.md, references/antigravity-tools.md, references/hermes-tools.md (first 5 of 6 lines)
Files the text names, such as ones to read or write. Found by matching words, so treat them as pointers.
What it leads to
- calls subagent-driven-development only when the human partner asks for cheaper orchestration, and only for a whole plan claude-code-tools.md, line 21
- requires brainstorming before entering plan mode line 22
- requires systematic-debugging when the request is a bug fix line 31
Other skills this one hands off to, calls, requires or offers instead, as a model read them.
Names skills outside this collection
- frontend-design line 28
Skills the text names that are not in this collection, as a model read them.
Licence
MIT, from LICENSE
The terms its author shares it under, which let it be shown here.
Other files in this skill (7) Close
The text
Most marks come from matching words in the file, so treat them as pointers.
<SUBAGENT-STOP> If you were dispatched as a subagent to execute a specific task, ignore this skill. </SUBAGENT-STOP>
<EXTREMELY-IMPORTANT> 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. </EXTREMELY-IMPORTANT>
Raw lines 1 to 17The 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 you haven't already brainstormed, invoke the brainstorming skill first.
Then announce "Using [skill] to [purpose]" and follow the skill exactly. If it has a checklist, create a todo per item.
Raw lines 18 to 25Skill Priority
When multiple skills apply, process skills come first — they set the approach, then implementation skills (frontend-design, etc.) carry it out. Brainstorming and systematic-debugging are Superpowers' most common process skills, but the rule holds for any of them.
- "Let's build X" → superpowers:brainstorming first, then implementation skills.
- "Fix this bug" → superpowers:systematic-debugging first, then domain skills.
Red Flags
These thoughts mean STOP—you're rationalizing:
| Thought | Reality |
|---|---|
| "This is just a simple question" | Questions are tasks. Check for skills. |
| "I need more context first" | Skill check comes BEFORE clarifying questions. |
| "Let me explore the codebase first" | Skills tell you HOW to explore. Check first. |
| "I can check git/files quickly" | Files lack conversation context. Check for skills. |
| "Let me gather information first" | Skills tell you HOW to gather information. |
| "This doesn't need a formal skill" | If a skill exists, use it. |
| "I remember this skill" | Skills evolve. Read current version. |
| "This doesn't count as a task" | Action = task. Check for skills. |
| "The skill is overkill" | Simple things become complex. Use it. |
| "I'll just do this one thing first" | Check BEFORE doing anything. |
| "This feels productive" | Undisciplined action wastes time. Skills prevent this. |
| "I know what that means" | Knowing the concept ≠ using the skill. Invoke it. |
Platform Adaptation
If your harness appears here, read its reference file for special instructions:
- Claude Code:
references/claude-code-tools.md - Codex:
references/codex-tools.md - Pi:
references/pi-tools.md - Antigravity:
references/antigravity-tools.md - Hermes Agent:
references/hermes-tools.md - Muse:
references/muse-tools.md
User Instructions
User instructions (CLAUDE.md, AGENTS.md, GEMINI.md, etc, direct requests) take precedence over skills, which in turn override default behavior. Only skip skill workflows or instructions when your human partner has explicitly told you to.
Raw lines 63 to 65From obra/superpowers at 2ce8aa1, 2026-10-21. Skills read by DeepSeek V4.1 Flash on 2026-11-04. Summary and techniques by Claude Opus 5.5 on 2026-11-06.