Skip to content

obra/superpowers / skills/diagnosing-superpowers

diagnosing-superpowers

Verified

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.

prompts/cost-and-time.md

View on GitHub
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.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall
subagent-driven-developmentobra/superpowersUse when executing implementation plans with independent tasks in the current sessionStars: 322kUpdated Claude CodeCodexVerifiedInstall