Essentials
Systematic Debugging
Listed under Software DevelopmentBug Fixing
Summary
Structured debugging: form hypotheses, gather evidence, bisect, and regress. Input is the failure symptom; output is an investigation log and root-cause conclusion. Suited to reproduce-and-locate work.
Why we picked it Why recommended
SkillPouch records why this skill was curated, stage by stage.
-
T14.s1Reproduce & locate
Alongside diagnosing-bugs—process skeleton vs tight feedback loop.
How to use Applicable stages
Use it in these workflow stages. Open a stage to return to its task.
Get and review
App deep-link installation is coming soon. Open the upstream repository to inspect the skill today.
Check the sources Evidence & sources
Public links you can open and verify on your own.
Upstream source
- Upstream repository (obra/superpowers) ↗ Verified on 2026-11-02
Boundaries Known limitations
Strip secrets and auth material first; do not speculate without evidence. Sample scripts are illustrative—do not run blindly in production.
Identity and license
License, review date, repository path, and stable identifier.