obra/superpowers / skills/diagnosing-superpowers
diagnosing-superpowers
VerifiedUse 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 6.8 KB |
| prompts/analyst-common.md | markdown | 1.5 KB |
| prompts/cost-and-time.md | markdown | 1.6 KB |
| prompts/plan-adherence.md | markdown | 1.6 KB |
| prompts/quality-evidence.md | markdown | 1.4 KB |
| prompts/repeated-work.md | markdown | 1.4 KB |
| prompts/request-conflicts.md | markdown | 1011 B |
| prompts/scrub-audit.md | markdown | 1.3 KB |
| prompts/scrub.md | markdown | 1.4 KB |
| prompts/similar-session.md | markdown | 1.7 KB |
| prompts/skill-timeline.md | markdown | 1.6 KB |
| prompts/stumbles.md | markdown | 1.3 KB |
| references/context-safety.md | markdown | 990 B |
| references/github-issues.md | markdown | 1.6 KB |
| references/redaction-policy.md | markdown | 2.2 KB |
| references/session-discovery.md | markdown | 1.8 KB |
| templates/bundle-README.md | markdown | 3.6 KB |
| templates/case.md | markdown | 2.9 KB |
| templates/issue.md | markdown | 2.6 KB |
| templates/report.md | markdown | 2.3 KB |
templates/issue.md
View on GitHubTitle: <skill or symptom>: <one-line observable> (<harness>)
- [x] I searched existing issues and this is not a duplicate (searched: <query terms>; closest: <#n title, or "none">)
## Who's filing this report? (required)
<model and harness of this session>, filing on behalf of <how your
partner wants to be named, or "my human partner">, who asked: "<their
request from this session that led to the diagnosis or the issue,
scrubbed>"
## Human-authored summary (required, under 200 words)
<Your partner's own words on what went wrong and what should have
happened, pasted as written. Ask for them; a placeholder here means the
issue is not ready to file. If they run long, ask them to trim rather
than editing their words.>
## Environment (required)
| Field | Value | Provenance / supporting evidence |
|-------|-------|-------------------------------|
| Superpowers version | <version> (<sha or "not a checkout">) | <historical evidence / unverified snapshot / current observation / unknown>; <location> |
| Harness (Claude Code, Cursor, etc.) | <harness> | <label>; <location> |
| Harness version | <version> | <label>; <location> |
| Your model + version | <model ids seen> | <label>; <location> |
| All plugins installed | <list> | <label>; <location> |
| OS + shell | <os version>, <shell> | <label>; <location> |
## Is this a Superpowers issue or a platform issue?
- [ ] I confirmed this issue does not occur without Superpowers installed
How I verified that this issue does not reproduce without Superpowers:
<"Not tried", or what your partner ran without superpowers and what
happened, with the transcript path if there is one. Tick the box above
only when a transcript shows the problem did not recur.>
Evidence for involvement is below; it does not establish cause.
## What happened?
<Problem statement, then the triage verdict, with `path:line` citations
rewritten as `transcript line <n>`.>
## Steps to reproduce
1. <first human prompt, scrubbed>
2. <the turns leading to the problem, one line each>
3. <the observable>
## Expected behavior
<from the problem statement>
## Actual behavior
<from the triage verdict>
## Debug log or conversation transcript
Session id(s): <ids>. Delivered local archive: <path, redaction level <level>
| none built>. Attached bundle: <no claim; attach only after approval>.
Superpowers involvement per the diagnosis report: <possible | likely>, with
evidence at <transcript lines>. This report does not propose a fix.
---
Filed with the `diagnosing-superpowers` skill. The filing model and
harness are under "Who's filing"; the diagnosed session's model, harness,
versions, and plugins are in the Environment table.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 471k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| 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 available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| subagent-driven-developmentobra/superpowersUse when executing implementation plans with independent tasks in the current session | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |