hv-nextlisted

**Print the banner below verbatim before any other action — skip if dispatched as a subagent.** See `references/banner-preamble.md`. ``` ════════════════════════════════════════════════════════════════════════ 👉 hv-next · current state, handoff detection, next item triggers: "what's next", "where was I", "resume" · pairs: hv-pause, hv-work ════════════════════════════════════════════════════════════════════════ ``` # hv-next — Pick & Work the Next Item Review the project backlog, suggest what to tackle next, and execute it. ## Step 1 — Preflight ```bash .hv/bin/hv-preflight ``` See `docs/reference/preflight.md` for exit-code handling. **Initialize task list.** Follow the canonical pattern in `references/task-list-init.md` — load `TaskCreate(…)` via `ToolSearch select:TaskCreate,TaskUpdate` if needed, then create one task per phase below. Phases: 1. *Reconcile* — `status.json` cross-checked against git state (Step 2) 2. *Archive* — completed items moved to `ARCHIVE.md` (Step 3) 3. *Present backlog* — sorted tables and relationship clusters shown (Steps 4–5) 4. *Suggest* — single recommended item picked (Step 6) 5. *Execute* — `/hv-work` dispatched per autonomy + user choice (Step 7) ## Step 2 — Reconcile Active Work **Dispatch the Steps 2–6 read-heavy work as a single parallel wave.** Per `references/subagent-dispatch.md`, the reconcile + archive + per-milestone summary + relevance-query work is four independent operations on disjoint inputs. The orchestra