Bug Triage Pack

A bug backlog is only as good as its triage — and most bugs arrive as "it's broken" with no repro, a panicked severity, and no idea who should look. This turns a raw report into a triaged item: reproducible steps, a severity and priority you can defend (not vibes), the environment that matters, a suspected area and owner queue, and a check for whether it's a duplicate — asking for what's missing instead of inventing it.

What This Skill Produces

• Normalized repro — clear, numbered steps; expected vs. actual; the minimal path to reproduce
• Severity & priority — each with reasoning (impact × frequency × workaround availability), not a gut number
• Environment & metadata — version, platform, browser/OS, user/role, first-seen, frequency
• Suspected area & owner queue — where it likely lives and who should take it next
• Duplicate/related check — is this the same as a known issue, and what to link
• Missing-info flags — what the reporter must supply before it's actionable

Required Inputs