hv-golisted

**Print the banner below verbatim before any other action — skip if dispatched as a subagent.** See `references/banner-preamble.md`. ``` ════════════════════════════════════════════════════════════════════════ ⚡ hv-go · capture and implement in one pass triggers: "fix X", "add Y", "do Z" · pairs: hv-capture, hv-work ════════════════════════════════════════════════════════════════════════ ``` # hv-go — Capture & Execute in One Pass ## Flow ``` Init guard → Capture → Clean-tree guard → Hand off to /hv-work ``` ## Step 1 — Preflight ```bash .hv/bin/hv-preflight ``` See `docs/reference/preflight.md` for exit-code handling. ## Step 2 — Capture Invoke `hv-capture` via the `Skill` tool. Prefix the args passed to capture with `(hv-go — cap clarification at 1-2 questions)` so capture applies the speed-path question limit; then pass the user's input verbatim. `hv-capture` handles classification, ID assignment, detail files, and the `BACKLOG.md` write. Capture runs before the clean-tree guard on purpose: `BACKLOG.md` lives under `.hv/`, which the clean-tree guard treats as a separate concern from the code paths it inspects, so capture never blocks Step 3. If Step 3 then fails, the item is safely on the backlog and the user can run `/hv-work` after cleaning up instead of re-describing it. Record the captured IDs (e.g., `[F05]`, `[B07]`) — you need them for Step 4. ## Step 3 — Guard: Clean Working Tree ```bash .hv/bin/hv-guard-clean "/hv-go" ``` Non-zero exit = stop