bug-fixlisted

# Bug Fix ## Overview Carries a bug from report to validated fix by chaining specialists: **investigate → decide → plan → implement**. You are the conductor. Investigation and implementation each go to a specialist wherever one is available, and this skill owns the seams and the evidence bar between them. **Core principle:** no fix is planned until the root cause is proven with `file:line` evidence, and no plan is written until the open questions are answered. **Do not guess.** A plausible fix for an unproven cause is worse than no fix: it consumes the report, closes the ticket, and leaves the bug live. ## When NOT to use - **Building new behaviour** — that is `superb:craft` then `superb:pipeline`. - **A change whose cause is already proven** — skip to the fix; the investigation exists to establish a cause, not to ceremonially confirm one. - **A whole feature's worth of bugs** — that is a phase of `superb:pipeline`, which has the fix loop, the findings ledger and the convergence rule. - **You only want to know what is wrong** — that is `superb:bug-investigate`, which runs this skill's Step 1 and stops. Reach for it when the decision to fix has not been made, or when naming the cause is the whole deliverable. ## Step 0 — Assemble the report The investigator needs five things. The invocation argument usually supplies one or two: | Field | Example | | ----- | ------- | | Symptom | "uploads over ~5MB fail silently" | | Reproduction | the steps, or `unknown` | | Er