This is a disciplined framework for debugging that forces you to find root causes before attempting fixes. It's built around four mandatory stages: root cause investigation, pattern analysis, hypothesis testing, and implementation. The iron rule is simple: no fix proposals until you complete stage one. It includes specific guardrails like adding diagnostic logging at component boundaries in multi-layer systems, tracing data flow backwards to find where bad values originate, and a hard stop after three failed fix attempts to question whether you have an architecture problem instead of a bug. The approach is opinionated about common shortcuts developers take under pressure, like skipping error messages or trying "just one quick fix" when time is tight.
npx skills add https://github.com/jnmetacode/superpowers-zh --skill systematic-debugging