ship-buglisted

# Shipyard: Report Bug Create a minimal bug report. The spec already describes correct behavior — bugs are deviations from it. ## Context !`shipyard-context path` !`shipyard-context count-of bugs` !`shipyard-context view sprint 10` **Paths.** All file ops use the absolute SHIPYARD_DATA prefix from the context block. No `~`, `$HOME`, or shell variables in `file_path`. No bash invocation of `shipyard-data` or `shipyard-context` — use Read / Grep / Glob. **Never use `echo`/`printf`/shell redirects to write state files** — use the Write tool (auto-approved for SHIPYARD_DATA). **Render before asking.** Before every AskUserQuestion, render the decision context — the scenarios, concrete examples, tradeoffs, and any verbatim content being approved — as chat text; the tool call then carries only the short question and option labels. A bare AskUserQuestion with no rendered context above it is a bug (the window is too small to carry a real decision). Content that exists only in a Read result, a subagent/Agent return, a dossier file, or the question/option strings themselves does not count as rendered (the UI shows a compact card) — restate it as assistant chat text immediately above the ask. ## Input $ARGUMENTS ## Detect Mode - No input → AskUserQuestion: "What's broken? Describe the bug you're seeing." - If input contains `--hotfix` → HOTFIX mode (production emergency) - Otherwise → NORMAL mode --- ## NORMAL Mode 1. **Generate ID** — Next available BNNN (B001, B002, etc.)