From ultrapowers
This skill should be used when encountering any bug, test failure, or unexpected behavior — before proposing fixes. Also appropriate when a previous fix attempt didn't work, when under time pressure to fix something, or when thinking 'just try changing X'.
npx claudepluginhub jaidhyani/jai-cc-plugins --plugin ultrapowersThis skill uses the workspace's default tool permissions.
Find root cause before attempting fixes. Symptom fixes are failure.
Verifies tests pass on completed feature branch, presents options to merge locally, create GitHub PR, keep as-is or discard; executes choice and cleans up worktree.
Guides root cause investigation for bugs, test failures, unexpected behavior, performance issues, and build failures before proposing fixes.
Writes implementation plans from specs for multi-step tasks, mapping files and breaking into TDD bite-sized steps before coding.
Find root cause before attempting fixes. Symptom fixes are failure.
No fixes without root cause investigation first. If the fix doesn't follow from understanding, it's a guess.
Read error messages completely. Stack traces, line numbers, error codes. They often contain the answer.
Reproduce consistently. What are the exact steps? Does it happen every time? If not reproducible, gather more data — don't guess.
Check recent changes. Git diff, new dependencies, config changes, environmental differences.
Check dependencies, config, and environment assumptions. Is the right version installed? Are env vars set? Is the config what you expect? Don't assume — verify.
Trace data flow. Where does the bad value originate? Trace backward through the call stack until the source is found. Fix at source, not at symptom.
In multi-component systems, add diagnostic logging at each component boundary before proposing fixes. Run once to see WHERE it breaks, then investigate that specific component.
ultrapowers:tdd).ultrapowers:verify).If 3+ fix attempts have failed, stop. This isn't a bug — it's an architectural problem. Each fix revealing a new issue in a different place is the pattern. Question fundamentals. Discuss with the user before attempting more fixes.
If the user says things like "stop guessing," "is that not happening?", "are we stuck?" — these mean you've skipped investigation. Return to Phase 1 immediately.
These thoughts mean stop and return to Phase 1: