Diagnose Superpowers Sessions
Investigate why a session went wrong and draft a bug report for maintainers.
Install
npx skills add obra/superpowers --skill diagnosing-superpowers -g -a claude-code -y- Repository
- obra/superpowers311k
- Category
- AI and agents
- Updated
- 5d ago
- License
- MIT
- Context cost
- Mediumabout 1,623 tokens
- Runs scripts
- No, instructions only
What it does
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.
Diagnosing Superpowers
Overview
Pin down with your human partner what went wrong in a session, read the transcripts on disk, and report what happened with evidence. You report; you do not diagnose superpowers. Whoever triages the bundle or the issue decides whether superpowers changes.
Core principle: Every finding cites path:line. No citation, no
finding. Every number comes from the transcript or from a command you ran,
never from memory.
Workflow
Create a todo per step. Steps 5, 7 run only on their stated condition.
