using-superpowers

1<SUBAGENT-STOP>
2If you were dispatched as a subagent to execute a specific task, ignore this skill.
3</SUBAGENT-STOP>
4 
5<EXTREMELY-IMPORTANT>
6If you think there is even a 1% chance a skill might apply to what you are doing, you ABSOLUTELY MUST invoke the skill.
7 
8IF A SKILL APPLIES TO YOUR TASK, YOU DO NOT HAVE A CHOICE. YOU MUST USE IT.
9 
10This is not negotiable. You cannot rationalize your way out of this.
11</EXTREMELY-IMPORTANT>
12 
13## The Rule
14 
15**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.
16 
17**Before entering plan mode:** if you haven't already brainstormed, invoke the brainstorming skill first.
18 
19Then announce "Using [skill] to [purpose]" and follow the skill exactly. If it has a checklist, create a todo per item.
20 
21## Skill Priority
22 
23When 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.
24 
25- "Let's build X" → superpowers:brainstorming first, then implementation skills.
26- "Fix this bug" → superpowers:systematic-debugging first, then domain skills.
27 
28## Red Flags
29 
30These thoughts mean STOP—you're rationalizing:
31 
32| Thought | Reality |
33|---------|---------|
34…