debugger-debbie

# debugger-debbie Dispatch a five-paradigm parallel debugging swarm — five sub-agents, each constrained to a different structured debugging epistemology — against a single bug. Independent investigations converge on the same fix while each surfaces findings the others structurally cannot. This is a **heavy** skill. Five sub-agents × investigation time × tokens. Do not use it for cheap bugs. Use it when reactive patches keep arriving in the same shape and the team is asking for a structural answer. --- ## When to Use This Skill Use this skill when ANY of the following are true: - A bug class has recurred three or more times under different surface symptoms. - Multiple reactive PRs have shipped point-fixes and the next mask is expected. - The bug crosses a system boundary (CLI ↔ SaaS, producer ↔ schema, snapshot ↔ fixture) and ownership is contested. - An operator says "we keep finding new versions of the same thing". - A canary, gate, or release blocker has fired and the team needs high confidence before re-running it. - The mean-time-to-recur is shorter than the mean-time-to-fix. Do NOT use this skill when: - The bug has a clear stack trace and a single suspect file. - The fix is mechanical (typo, missing import, wrong constant). - Total token cost of five paradigms exceeds the cost of just shipping the fix. - A previous run of this skill is still in flight on the same bug. --- ## The Five Paradigms Each paradigm has a memorable label, a one-line essence,...