issue-debug
Mission
Section titled “Mission”Diagnose and fix problems: reproduce → locate → understand → fix → prevent recurrence.
When to Use
Section titled “When to Use”Use when something is broken, producing wrong output, crashing, behaving unexpectedly, or when you need to trace a failure to its root cause.
Triggers: “something is broken”, “this is failing”, “why does this crash”, “unexpected output”, “trace this error”, “find the bug”
Skills Invoked
Section titled “Skills Invoked”Sequential debug workflow:
debug-assistant(Zero-Cost) — symptom triage, top-3 hypothesesdebug-root-cause(Advanced) — causal chain analysisdebug-reproduction(Efficient) — minimal reproducible exampledebug-postmortem(Efficient) — post-incident report with prevention measures
Chain-To
Section titled “Chain-To”test-verify— add regression tests to prevent recurrencecode-refactor— structural fix if root cause is design-levelpolicy-govern— escalate if root cause is a security issue
Example
Section titled “Example”{ "request": "The checkout service is throwing 500 errors intermittently when processing Stripe webhooks"}Output: Triage hypothesis list, root cause finding, minimal reproduction script, and a postmortem with three action items.