diagnosing-superpowers

Diagnosing Superpowers

Diagnosing Superpowers is an agent skill from Superpowers that reads a session's transcripts when work went wrong and reports what happened, with every finding tied to a file and line.

Checked by CookiesForAI on : license and last change of the skill re-read from GitHub.

Written by

Install Diagnosing Superpowers

Install only this skill with the skills CLI

Terminal
npx skills add obra/superpowers --skill diagnosing-superpowers

Or, in Claude Code, install the whole Superpowers plugin from Anthropic's official marketplace

Agent chat
/plugin install superpowers@claude-plugins-official

Or paste this into your coding agent: Install the agent skill diagnosing-superpowers from github.com/obra/superpowers. Checked by CookiesForAI on : license and last change of the skill re-read from GitHub. A skill can include scripts that run on your computer, so read its source first.

What Diagnosing Superpowers does

Diagnosing Superpowers is one of the skills in Superpowers, Jesse Vincent's open-source method for AI coding agents. It loads when a Superpowers session went wrong and you want to know why: repeated work, an ignored plan, a skill that never fired, a session that took too long or cost too much. It works on the current session or a past one named by id or path, and it can prepare a bug report for the Superpowers maintainers.

In Diagnosing Superpowers, the agent first asks you one question at a time until it can state the problem, then finds the session files on disk and fills a case file under ~/.superpowers/diagnosing-superpowers/. It dispatches seven analyst subagents in parallel, one per dimension: skill timeline, plan adherence, repeated work, stumbles, quality evidence, request conflicts, and cost and time. A finding without a file path and line is dropped, and session files are never modified.

The Diagnosing Superpowers result is a report filled from a bundled template. The skill reports and does not diagnose: it states whether Superpowers was involved, but never names a defect in a skill or proposes a change. When Superpowers may be involved, or when you ask, it searches GitHub issues and drafts a new one, created only after you approve the exact text. On request it builds a bundle of the session with emails, names, secrets and private paths replaced, and reminds you that scrubbing can miss things.

When to use Diagnosing Superpowers

  • You want to know why an agent session took so long or cost so much.
  • Your agent ignored the plan, repeated work, or never used a skill you expected.
  • You want to check what a session that is still running is actually doing.
  • You want to file a bug report with the Superpowers maintainers, backed by evidence from the transcript.

When to pick something else

  • You want to debug your own code rather than an agent session: use Systematic Debugging.

Which agents Diagnosing Superpowers works in

Jesse Vincent documents Diagnosing Superpowers for Claude Code, Codex (app and CLI), Cursor, Gemini CLI, GitHub Copilot CLI, OpenCode, Antigravity, Devin CLI, Factory Droid, Grok Build CLI, Kimi Code, Pi, Qwen Code, Hermes Agent, Muse. The open skills CLI also installs it into 78 agents, including Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode (we listed it with the CLI on ). See where each agent looks for skills.

Superpowers is written in Claude Code's vocabulary (subagent dispatch, todos, the Skill tool) and ships tool mappings for Codex, Gemini CLI, Pi, Antigravity, Hermes Agent and Muse. Installed as the full plugin, a session-start hook loads Using Superpowers so the agent reaches for skills on its own; one skill installed with the skills CLI gets no hook and may point to sibling skills you do not have. This skill needs a subagent tool: Claude Code's Agent tool, or in Codex the multi-agent feature switched on in config.toml (multi_agent = true).

Diagnosing Superpowers license

Diagnosing Superpowers is published under MIT.

More from Jesse Vincent

Lists that include diagnosing-superpowers