domains / families / agent-tooling / diagnosing-superpowers

diagnosing-superpowers

separate

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.

When to use

• diagnosing why a superpowers session went wrong
• investigating repeated work or ignored plans
• analyzing stumbles or poor results
• checking if a skill fired
• investigating high cost or long duration
• building a bug report for superpowers maintainers
• analyzing current or past sessions by id or path

When not to use

• diagnosing superpowers defects
• proposing changes to skills
• modifying, moving, or deleting session files
• building a bundle unprompted
• creating GitHub issues without approval

Skill page

Source