Skip to content

Trevoke/org-gtd.el / .claude/skills/using-superpowers

using-superpowers

Verified

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 MUST USE IT.

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

Using Skills

The Rule

Check for skills BEFORE ANY RESPONSE. This includes clarifying questions. Even 1% chance means invoke the Skill tool first.

Development Workflow Skills

These skills form a pipeline. Each phase produces a dated artifact and references the next step:

SkillWhen to Use
/defineNew feature request, bug report, or requirement to break down
/architectRequirements exist, need technical design
/implementDesign exists, ready to build
/qaImplementation complete, need adversarial testing
/refactorCode quality pass after implementation

You don't always need all phases. Start at whichever phase makes sense.

Red Flags

These thoughts mean STOP — you're rationalizing:

ThoughtReality
"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.
"This doesn't need a formal skill"If a skill exists, use it.
"The skill is overkill"Simple things become complex. Use it.
"I'll just do this one thing first"Check BEFORE doing anything.

Skill Priority

When multiple skills could apply:

  1. Process skills first (define, architect) — determine HOW to approach
  2. Implementation skills second (implement, qa, refactor) — guide execution

Skill Types

Rigid (TDD, qa): 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.

reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 467kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 319kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 319kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 319kUpdated Claude CodeCodexVerifiedInstall