Install
npx skills add obra/superpowers --skill diagnosing-superpowers
Runs the open skills CLI and installs the skill for your agent (Claude Code, Codex, Cursor …). Alternatively copy the skill folder into .claude/skills/ or upload it in Claude.ai under Settings → Skills.
As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-official
/plugin install superpowers@superpowers-dev
This skill is part of the plugin “superpowers”. In Claude Code the plugin installs it together with the plugin’s other skills, commands and hooks.
What does the diagnosing-superpowers skill do?
Description from the SKILL.md in the source repository.
Questions about diagnosing-superpowers
What does the diagnosing-superpowers skill do?
Use 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.
How do I install diagnosing-superpowers?
In a terminal: npx skills add obra/superpowers --skill diagnosing-superpowers. The skills CLI asks which agents to install it for. In Claude.ai you can upload the skill folder as a ZIP under Settings → Skills.
Which agents can use diagnosing-superpowers?
Skills use the open SKILL.md format, which Claude Code, Claude.ai, the Claude API, OpenAI Codex, Cursor, Gemini CLI and other agents support.
Is diagnosing-superpowers safe to use?
Our automatic check found no risky patterns (piped shell scripts, hidden characters, secret access, prompt overrides). It is not a full audit – read the SKILL.md and any scripts before installing.
More skills from obra/superpowers
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Use when you have a spec or requirements for a multi-step task, before touching code
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Use when implementing any feature or bugfix, before writing implementation code
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
Related skills in Other
No description in the SKILL.md.
A relentless interview to sharpen a plan or design.
No description in the SKILL.md.
No description in the SKILL.md.
No description in the SKILL.md.
No description in the SKILL.md.
No description in the SKILL.md.
No description in the SKILL.md.