Diagnosing Superpowers investigates a coding-agent session that misbehaved: a skill fired when it should not, stayed silent, the plan was ignored, work repeated, or cost more than expected. It interviews you first, locates the transcripts on disk, runs analyst subagents across seven dimensions and writes a report where every finding cites a file and line.
What You Get
- A problem statement agreed with you before any analysis
- A report with line-cited findings from seven analyst dimensions
- A search of existing GitHub issues with a suggested match
- An optional scrubbed bundle at a redaction level you choose, audited before archiving
- An optional search for similar sessions
Common Use Cases
- Working out why a session was slow or expensive
- Finding out why a skill never fired
- Preparing a bug report for the superpowers maintainers
What Makes It Unique
Every finding must cite a path and line, and every number must come from the transcript or a command it ran. The skill reports and stops: it never proposes a change to superpowers, and it builds an export bundle only when you ask.
Under The Hood
Instructions with prompt files for subagents, templates and references. The agent reads session transcripts from disk without modifying them, using a method that guards its context against very long lines, and writes a case file and report under ~/.superpowers/diagnosing-superpowers. For issues it uses the gh command-line tool after you approve the text, and for export it runs scrub and audit subagents and then zip or tar on your approval.