What the test showed
On a bug contained in one small module, the skills did not change the result: every run found the cause, fixed a related bug nobody had reported, and added regression tests. Plain Claude did the same.
When these skills should matter
Both skills are written for hard bugs. Superpowers' systematic-debugging forbids any fix before the root cause is found and works in four phases: root-cause investigation, pattern analysis, testing one hypothesis at a time, then the fix. Matt Pocock's diagnosing-bugs puts building a fast pass/fail feedback loop first, then reproducing and minimising the bug, forming hypotheses, instrumenting, and fixing with a regression test.
That discipline pays off on bugs that are slow to reproduce, intermittent, or spread across systems. We plan to test them on a harder bug.


