# Using Superpowers

Explain how to find and invoke the skills that apply to a task.

- Repository: https://github.com/obra/superpowers (310584 stars)
- Category: AI and agents
- License: MIT
- Last updated: 2026-10-29
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add obra/superpowers --skill using-superpowers -g -a claude-code -y`
Codex: `npx skills add obra/superpowers --skill using-superpowers -g -a codex -y`
Cursor: `npx skills add obra/superpowers --skill using-superpowers -g -a cursor -y`
Gemini CLI: `npx skills add obra/superpowers --skill using-superpowers -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add obra/superpowers`

## Description

Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

<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>

## 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 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.

## Skill 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:

The rest: https://github.com/obra/superpowers/blob/HEAD/skills/using-superpowers/SKILL.md