AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

diagnosing-superpowers

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.

Original source
obra
License
MIT
Pinned revision
2ce8aa15d05bd57213e6f746f953aafb7ded7a8b

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

Ask your assistant

Use Agentic Memory skills to read obra--diagnosing-superpowers at revision 2ce8aa15d05bd57213e6f746f953aafb7ded7a8b, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 20

templates/report.md

Session diagnosis:

Report path: ~/.superpowers/diagnosing-superpowers//report.md Written:

1. Problem statement (REQUIRED)

2. Triage verdict (REQUIRED)

<What the evidence shows happened around the reported problem. Prose, with path:line after every claim. State confidence: high / medium / low, and what would raise it. No statement about what superpowers should do.>

3. Environment (REQUIRED)

  • OS:
  • Harness and version:
  • Models seen:
  • Superpowers install root / version / git sha:
  • Skill files read or injected (sha1 table from the case file):
  • Other plugins, extensions, MCP servers:
  • Instruction files present (paths only):

Label every environment field and skill observation as historical evidence, unverified snapshot, current observation, or unknown, and record its supporting evidence location.

4. Sessions examined (REQUIRED)

| Role | Session id | Absolute path | Lines | Bytes | |---|---|---|---|---|

Rejected candidates: <id — path — why>, or "none".

5. Timeline (REQUIRED)

One row per human-typed prompt. Events column lists skills invoked, subagents dispatched, compaction, errors, resumes, aborts.

| Turn | Line | Time | Request (one line) | Events | |---|---|---|---|---|

6. Findings (REQUIRED, one subsection per dimension)

Each finding:

- finding: <one sentence>
  evidence: <path:line> — "<short quote>"
  turns: <first>–<last>
  confidence: high | medium | low

A dimension with nothing to report says none found — checked: <what was checked>.

6.1 Skill timeline

6.2 Plan adherence

6.3 Repeated work

6.4 Stumbles

6.5 Quality evidence

6.6 Request conflicts

6.7 Cost and time

6.8 Other plugins and skills used

7. Superpowers involvement (REQUIRED)

not indicated | possible | likely

Evidence lines: <path:line list>. This section states involvement only. It does not name a defect and does not propose a change.

8. Coverage notes (REQUIRED)

  • Not read: <ranges, files, and why>
  • Harness features unavailable:
  • Session was in progress at read time: yes/no
  • For your human partner to double-check:

9. Similar sessions (only when requested)

| Session id | Path | Date | Harness | Matched | Did not match | |---|---|---|---|---|---|