What problem does it solve? When users report bugs verbally, key details like reproduction steps, expected versus actual behavior, and severity often get lost or mixed with premature root-cause guesses. This Skill turns a vague complaint into a structured, traceable {slug}-report.md file that downstream root-cause analysis can rely on. ## Core Features & Use Cases - Five-question guided intake: Asks about symptoms, reproduction steps, expected vs actual behavior, environment, and severity one at a time, with ambiguity checks that force concrete answers. - Fast-track triage: Reads the relevant code early to decide whether the issue qualifies for a quick fix path (single root cause, 1-2 line change) or needs the standard full-report workflow. - Structured report generation: Produces a Markdown issue report with YAML frontmatter (doc_type, severity, summary, tags) and explicit exit criteria before handoff to the analysis phase. - Use Case: A user says "the submit button sometimes shows a blank popup." The Skill walks them through reproduction conditions, records expected vs actual behavior separately, assigns a P1 severity, and writes a confirmed issue report ready for root-cause analysis. ## Quick Start Tell the assistant "I found a bug, help me file an issue" and describe the symptom you observed.
