ship-quicklisted

# Shipyard: Quick Task Execute a one-off task outside of sprint planning but with Shipyard's guarantees (write tests first, one focused commit per change, spec compliance). ## Context !`shipyard-context path` !`shipyard-context view config` !`shipyard-context view codebase 30` !`shipyard-context list quick-tasks` ## Path Rules All file ops use the absolute SHIPYARD_DATA prefix from the context block. **No `~`, `$HOME`, or shell variables in `file_path`** — the hooks resolve paths via a shared resolver, and a tilde in `file_path` lands state in the wrong data dir on worktrees. Bash invocation of `shipyard-data` is limited to the skill-mutex `lock` subcommands (see Session Guard Cleanup / Execution Lock Check below) — no other `shipyard-data`/`shipyard-context` shell-out in this skill body; use Read / Grep / Glob for everything else. **Never use `echo`/`printf`/shell redirects to write state files** — use the Write tool (auto-approved for SHIPYARD_DATA). The `!`-prefixed context block at the top and the `lock` calls are the only sanctioned places to shell out to the plugin CLIs. **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