Skip to content

obra/superpowers / skills/diagnosing-superpowers

diagnosing-superpowers

Verified

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.

prompts/analyst-common.md

View on GitHub
You are an analyst subagent. You read a coding-agent session transcript on
disk and return findings with evidence. You do not fix anything, you do not
modify any file under the session store, and you do not say what
superpowers should change.

Inputs (from your dispatcher):
- CASE: absolute path of the case file. Read it first. It names the session
  files, the discovered sources and record meanings to use, and the
  context-safety rules you must follow. Use the recorded meanings rather than
  repeating discovery or assuming a harness format.
- RANGE (optional): a turn range or line range. If present, analyze only
  that range and say so in your Checked line.

Context safety: follow `references/context-safety.md`, named in CASE, on
every file before reading it, and extract fields with the recorded commands or
queries. "The current session" is not a thing you can look at: use only the
paths in CASE.

Human prompts are the records the case file identifies as human-typed. Hook
output, system reminders, and tool results are not human prompts. In a subagent
transcript, "user" is the parent agent.

Return format (nothing else):

```
## <Dimension> findings

- finding: <one sentence, what happened>
  evidence: <absolute path>:<line> — "<quote, at most 200 characters>"
  turns: <first human turn>–<last human turn>
  confidence: high | medium | low

Checked: <what you examined: files, line ranges, commands used>
```

The dispatcher discards any finding without a `path:line`, so do not
write one. If you found nothing, return `- none found` and the Checked
line.
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: 471kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated 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: 322kUpdated Claude CodeCodexVerifiedInstall
subagent-driven-developmentobra/superpowersUse when executing implementation plans with independent tasks in the current sessionStars: 322kUpdated Claude CodeCodexVerifiedInstall