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.

references/session-discovery.md

View on GitHub
# Discover the session history

Resolve the session your human partner named using the tools and information
available in this environment. Your knowledge can suggest where to look; verify
the result against the actual history.

Use the harness's exposed session tools, configured storage, local help,
documentation, or bounded filesystem inspection. Measure files before reading
their content and follow context-safety.md. Inspect archives or indexes when the
environment points to them. A supplied usable path does not need another search.

Confirm identity using the available session id, working directory, timestamps,
and matching conversation content. Recency alone is not confirmation. Distinguish
the requested session from its children and unrelated candidates. Ask for a
missing identifying fact when the available evidence cannot distinguish them.

For each filesystem source, obtain its full absolute path from the environment,
with home-directory shorthand and variables expanded. Use that same path in the
case record and in the discovery answer you give your human partner.

Establish the record meanings needed for the requested investigation from
observed records or documentation. Distinguish human messages from injected
messages, tool results, and a parent agent's dispatch. Match tool calls to their
results. Establish usage-counter semantics before calculating totals. Do not
infer a format from another harness or turn a missing field into a zero.

Record the exact sources, relevant field meanings, supporting record locations,
associated sessions, rejected plausible candidates, and unresolved information
in the case file. Subsequent readers use that record rather than repeating
discovery. If history is missing, inaccessible, or ambiguous, state the specific
limitation and ask for the missing path, export, or identifying detail.
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: 471kUpdated 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