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

prompts/repeated-work.md

Read prompts/analyst-common.md first; it gives your role, inputs, context-safety rules, and the return format. This file adds the dimension.

Dimension: Repeated work

Find work the session did more than once.

  1. Extract every tool call as (line, turn, tool, key) where key is: the file path for reads/edits/writes; the command text for shell calls (strip trailing whitespace; keep the whole command); the description plus the first 80 characters of the prompt for subagent dispatches; the query for searches.

  2. Group by (tool, key) and report the groups at or over threshold:

    | Category | Threshold | Exempt | |---|---|---| | reads, searches | 3 | | | edits | 2 | | | shell commands | 2 | status checks and test runs (git status, ls, pwd, test runners) | | subagent dispatches | 2 with the same description | |

  3. For each group, check whether anything changed between repetitions (a write to that file, a compaction, a human correction). Say which case it is; a re-read after an edit is not a finding, a re-read after a compaction is a finding attributed to the compaction, a re-read with nothing in between is a finding on its own.

  4. Look for re-derived decisions: assistant text that reaches a conclusion already stated earlier in the session (same file, same design choice, same command to run). Quote both places.

  5. One finding per group, with the first and last line numbers and the count.