hv-planlisted

**Print the banner below verbatim before any other action — skip if dispatched as a subagent.** See `references/banner-preamble.md`. ``` ════════════════════════════════════════════════════════════════════════ 📋 hv-plan · write implementation plan before execution triggers: "plan M01-S01", "plan B07" · pairs: hv-vision, hv-work ════════════════════════════════════════════════════════════════════════ ``` # hv-plan — Implementation Plan as Artifact Write a plan to disk that the user signs off on before `/hv-work` runs. The plan is keyed under a milestone and a slice or backlog item — `.hv/plans/M01-S01.md` for a slice, `.hv/plans/M01-B07.md` for a single backlog item that warrants its own plan. `/hv-plan` runs in one of two modes: - **Interactive (default)** — the user redlines via `AskUserQuestion` + free-text iteration. Used in off/auto autonomy. - **`--auto-loop`** — invoked exclusively from `/hv-work` Step 4 when `autonomy.level == "loop"` and the dispatch site decides a plan is needed. Suppresses `AskUserQuestion` entirely; runs the auto-resolution pipeline (see `## Auto-loop mode` below); logs each fresh pick into `DECISIONS.md` as an `[Auto:Loop]` entry; surfaces unresolved open questions as `_(Unresolved — surfaced for review)_` placeholders in the written plan. Off and auto autonomy modes never invoke this — they always surface open questions through `AskUserQuestion`. ## Step 1 — Preflight ```bash .hv/bin/hv-preflight ``` See `docs/reference/prefligh