diagnosing-superpowers

1# Diagnosing Superpowers
2 
3## Overview
4 
5Pin down with your human partner what went wrong in a session, read the
6transcripts on disk, and report what happened with evidence. You report;
7you do not diagnose superpowers. Whoever triages the bundle or the issue
8decides whether superpowers changes.
9 
10**Core principle:** Every finding cites `path:line`. No citation, no
11finding. Every number comes from the transcript or from a command you ran,
12never from memory.
13 
14## Workflow
15 
16Create a todo per step. Steps 5–7 run only on their stated condition.
17 
181. **Problem intake.** Ask one question at a time until you can write a
19   statement naming the session(s), the turn range if known, what your
20   partner expected, what happened, and the observable they care about
21   (wall-clock, tokens, repeated actions, one specific action). "It took
22   too long" is a complaint, not a problem statement. Note whether the
23   goal is a superpowers bug report.
242. **Locate.** Resolve each session to verified absolute filesystem paths using
25   `references/session-discovery.md`. Confirm a past session by quoting its
26   first prompt and timestamp, and list every candidate you rejected with the
27   reason, or "none". Enumerate subagent transcripts. Create
28   `~/.superpowers/diagnosing-superpowers/<session-id>/`, tell your
29   partner the path, and fill `templates/case.md` there, following its
30   provenance rules for environment and skill observations.
31…