diagnosing-superpowers

Topics in the source

• Diagnosing Superpowers
• Overview
• Workflow
• Quick reference
• Hard rules
• Red Flags

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. Create a todo per step. Steps 5–7 run only on their stated condition. 1. Problem intake. Ask one question at a time until you can write a statement naming the session(s), the turn range if known, what your partner expected, what happened, and the observable they care about (wall-clock, tokens, repeated actions, one specific action). "It took too long" is a complaint, not a problem statement. Note whether the goal is a superpowers bug report. 2. Locate. Resolve each session to verified absolute filesystem paths using references/session-discovery.md. Confirm a past session by quoting its first prompt and timestamp, and list every candidate you rejected with the reason, or "none". Enumerate subagent transcripts. Create /.superpowers/diagnosing-superpowers/ /, tell your partner the

This is an excerpt. Refer to the complete source and its current requirements.