Diagnosing Superpowers
by obra5bf4e7801107No license290K starsListed Sep 23, 2026Updated Sep 23, 2026Repository updated yesterday
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.
- 5bf4e7801107Currentcommit 5bf4e78Published Sep 23, 2026
Source and attribution
Source:obra/superpowersinskills/diagnosing-superpowersat commit5bf4e78
License: No license
Content belongs to its original authors. SourceWeft indexes it from a public repository.
More from obra/superpowers
Writing Plans
obra
Use when you have a spec or requirements for a multi-step task, before touching code
Verification Before Completion
obra
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
Using Superpowers
obra
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
Using Git Worktrees
obra
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback
Test Driven Development
obra
Use when implementing any feature or bugfix, before writing implementation code
Requesting Code Review
obra
Use when completing tasks, implementing major features, or before merging to verify work meets requirements