StealIt

Diagnosing Superpowers

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.

Install

Run this in your project folder. It works with Claude Code, Cursor, Codex and dozens of other agents.

$ npx skills add obra/superpowers --skill diagnosing-superpowers

Needs Node.js. Add -g to install for every project, or -a claude-code to skip the agent picker.

How to use Diagnosing Superpowers

Once it's installed, Claude reads this skill on its own whenever a request matches what it's for, so you don't have to mention it by name. In Claude Code you can also run it directly by typing /diagnosing-superpowers.

It contains no scripts, only instructions and reference files, so it can't run code on its own.

What the instructions cover

  1. 1Overview
  2. 2Workflow
  3. 3Quick reference
  4. 4Hard rules
  5. 5Red Flags

Section headings from the skill's SKILL.md file.

What's inside · 20 files

  • SKILL.md
  • prompts/analyst-common.md
  • prompts/cost-and-time.md
  • prompts/plan-adherence.md
  • prompts/quality-evidence.md
  • prompts/repeated-work.md
  • prompts/request-conflicts.md
  • prompts/scrub-audit.md
  • prompts/scrub.md
  • prompts/similar-session.md
  • prompts/skill-timeline.md
  • prompts/stumbles.md
  • references/context-safety.md
  • references/github-issues.md
  • references/redaction-policy.md
  • references/session-discovery.md
  • templates/bundle-README.md
  • templates/case.md
  • templates/issue.md
  • templates/report.md

More from Jesse Vincent

See all →

BrainstormingTop pick

You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it…

Coding WorkflowJesse Vincent312k

Systematic DebuggingTop pick

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

Coding WorkflowJesse Vincent312k

Dispatching Parallel Agents

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

AI & AgentsJesse Vincent312k

Executing Plans

Use 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

Coding WorkflowJesse Vincent312k
See all →

Grill MeTop pick

A relentless interview to sharpen a plan or design.

Coding WorkflowMatt Pocock313k

CavemanTop pick

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop…

Coding WorkflowJulius Brussee117k

PonytailTop pick

Lazy senior dev mode: the smallest change that fully solves the task, and a reply a busy human understands in one read. Use on any coding task (writing, fixing, refactoring…

Coding WorkflowDietrich Gebert184k

Ponytail Audit

Quality audit of a whole repo: bugs, security holes, what breaks under real load, risky code without tests, slow paths, and what to delete, merge or split. Ranked, each finding…

Coding WorkflowDietrich Gebert184k