writelisted

## Pre-computed context Current branch: !`git branch --show-current 2>/dev/null || echo "unknown"` Working tree: !`git status --porcelain 2>/dev/null | head -5 || echo "clean"` ## Variables Arguments: `$ARGUMENTS` ## Purpose `/bug-report` produces a five-field structured report so the next session (or a human) can act without re-asking on vague repro, missing severity, no fix location, or hand-wavy expected/actual. **Read-only** — it captures, it does not fix, and it does not file (unless you explicitly ask). This is the **bug-intake** stage. It sits upstream of filing the report into a work-item tracker, and it is independent of any downstream fix workflow — when the report itself is the deliverable (a Slack message, a PR comment, a verbal handoff), that is all this skill needs to do. Five fields: title, steps to reproduce, expected vs actual, severity (with justification), and suggested fix location. A `(unknown — needs reporter confirmation)` placeholder is used for any field that cannot be backed from the source, rather than inventing one. A sharp report captured up front saves the next session from re-asking. Unrepresented reproduction steps cost far more to recover later than to capture now. ## Trigger conditions — when to invoke Invoke when ANY hold: - The user describes a defect ("there is a bug in `X`", "`X` is broken when `Y`") - The user asks for help filing/writing-up a bug ("how do I report this", "write this up") - The user states a behavioural mismat