Catalog
obra/using-superpowers

obra

using-superpowers

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

NewUpdated Sep 19, 2026

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

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.

Files8
8 files · 18.1 KB

Select a file to preview

Overall Score

79/100

Grade

B

Good

Grades are signals, not a certification. Always review a skill yourself before use.

Safety

82

Quality

76

Clarity

87

Completeness

68

Summary

This is a meta-skill that instructs AI agents on how to discover and use other skills. It establishes a mandatory workflow: **before any response, action, or clarifying question**, check for applicable skills and invoke them. The skill emphasizes absolute priority ("not negotiable", "cannot rationalize") and includes platform adaptation instructions for multiple AI agent harnesses (Claude Code, Codex, Hermes, Gemini CLI, Muse, Pi, Antigravity).

Detected Capabilities

skill invocation routingmulti-platform tool mappingtask/todo tracking abstractionsubagent dispatch coordinationinstruction file resolution

Trigger Keywords

Phrases that agents use to match this skill to user intent.

initialize agent workflowcheck for applicable skillsskill routing decisionmulti-platform setupagent bootstrapping

Risk Signals

WARNING

Aggressive instruction override enforcement ('ABSOLUTELY MUST', 'cannot rationalize', 'not negotiable')

SKILL.md lines 8-14
INFO

Prompt injection risk: skill instructs agent to ignore subagent dispatch boundaries if certain conditions are met

SKILL.md lines 6-7 ('<SUBAGENT-STOP>' directive)
INFO

Conditional instruction: directive to ignore skill workflows if user has given explicit instructions

SKILL.md lines 63-65 ('User Instructions' section)

Use Cases

  • Initialize multi-skill workflows on any agent platform
  • Enforce mandatory skill-checking discipline in complex tasks
  • Map skill abstractions to platform-specific tools
  • Prevent agents from skipping structured approaches

Quality Notes

  • Platform reference files are well-structured and mapped correctly to tool abstractions, reducing agent confusion
  • Red Flags table is exceptionally clear and directly addresses common rationalizations agents make
  • Skill Priority hierarchy is explicit and gives concrete examples (superpowers:brainstorming first, then implementation skills)
  • Comprehensive coverage of 7 agent platforms (Claude Code, Codex, Hermes, Gemini, Muse, Pi, Antigravity) with platform-specific tool mappings
  • Instructions are prescriptive but may feel oppressive to some users due to emphatic 'non-negotiable' language
  • Missing: explicit guidance on how an agent should behave if NO applicable skill exists
  • Missing: how to handle skill conflicts or mutual exclusivity
Model: claude-haiku-4-5-20251001Analyzed: Sep 19, 2026

Reviews

Add this skill to your library to leave a review.

No reviews yet

Be the first to share your experience.

Version History

  1. v2.2

    Content updated

    ✦ AIAdds support for Claude Code and Muse platforms with new reference files detailing platform-specific instructions.

    2026-09-19

    LATEST
  2. v2.1

    Content updated

    ✦ AIRemoves priority hierarchy documentation and simplifies skill invocation rule; reorganizes platform references and reduces enforcement language.

    2026-09-09

    View This Version
  3. v2.0

    Contract changed: description

    ✦ AIAdds multi-platform tool reference files (Codex, Gemini, PI, Antigravity) and shifts from naming tools by platform to action-oriented language. Documentation and flowchart refined for clarity.

    triggering2026-06-28

    View This Version
  4. v1.0

    2026-05-02

    View This VersionInitial version

Use obra/using-superpowers in your dev environment

Command Palette

Search for a command to run...