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/cost-and-time.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: Cost and time

Account for where tokens and wall-clock went.

  1. Tokens. Use only the usage records and counter meanings established in the case file. State whether each counter is incremental or cumulative before calculating totals; difference cumulative observations without turning a missing observation into zero. Report the five turns with the largest supported totals and the supported totals per associated session.
  2. Wall-clock. Use the evidenced timestamp fields, event boundaries, and units recorded in the case file. Report the five longest supported turns and any gap longer than ten minutes between consecutive events (idle, waiting on an associated session, or waiting on your human partner; say which only when the records show it).
  3. Largest tool results: use the case file's evidenced tool-result records to report the ten largest results with their tool and turn. Measure records before extracting bounded content.
  4. Compactions: count and locate records whose meaning as compaction events was established during discovery. Report available before/after counters and what the session was doing when each fired; mark unsupported fields absent.
  5. Associated sessions: count them and report supported usage, duration, and dispatching turn for each.
  6. Report the turns, subagents, tools, or repeats that dominate the totals, with numbers. Do not speculate about why a turn was expensive beyond what the transcript shows.