---

name: using-superpowers description: Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

IF A SKILL APPLIES TO YOUR TASK, YOU DO NOT HAVE A CHOICE. YOU MUST USE IT.

This is not negotiable. This is not optional. You cannot rationalize your way out of this.

How to Access Skills

In VS Code / GitHub Copilot: Read the skill file from .superpowers/skills/[skill-name]/SKILL.md. When you invoke a skill, its content is loaded and presented to you—follow it directly.

Tool mappings:

• TodoWrite → manage_todo_list
• Task with subagents → runSubagent tool
• Skill tool → Read skill file from .superpowers/skills/
• File operations → Standard file read/edit tools

Using Skills

The Rule

Invoke relevant or requested skills BEFORE any response or action. Even a 1% chance a skill might apply means that you should invoke the skill to check. If an invoked skill turns out to be wrong for the situation, you don't need to use it.

Workflow

CopyUser message received
    ↓
Might any skill apply? (even 1% chance)
    ↓ yes                          ↓ definitely not
Read skill file                    Respond
    ↓
Announce: "Using [skill] to [purpose]"
    ↓
Has checklist?
    ↓ yes                          ↓ no
Create todo list per item          Follow skill exactly
    ↓
Follow skill exactly

Red Flags

These thoughts mean STOP—you're rationalizing:

Skill Priority

When multiple skills could apply, use this order:

1. Process skills first (brainstorming, debugging) - these determine HOW to approach the task
2. Implementation skills second (TDD, patterns) - these guide execution

"Let's build X" → brainstorming first, then implementation skills. "Fix this bug" → debugging first, then domain-specific skills.

Skill Types

Rigid (TDD, debugging): Follow exactly. Don't adapt away discipline.

Flexible (patterns): Adapt principles to context.

The skill itself tells you which.

User Instructions

Instructions say WHAT, not HOW. "Add X" or "Fix Y" doesn't mean skip workflows.