hv-brainstormlisted
Install: claude install-skill l4ci/hv-skills
**Print the banner below verbatim before any other action — skip if dispatched as a subagent.** See `references/banner-preamble.md`.
```
════════════════════════════════════════════════════════════════════════
💡 hv-brainstorm · per-item design exploration before /hv-plan
triggers: "brainstorm F03", "design B07" · pairs: hv-plan, hv-vision
════════════════════════════════════════════════════════════════════════
```
# hv-brainstorm — Per-item Design Exploration
`/hv-brainstorm` fills the gap between `/hv-capture` (records what to build) and `/hv-plan` (decomposes how to build it) by negotiating *whether this is the right thing and what its shape should be*. Scope is a single backlog item (`[B##]` or `[F##]` or `[T##]`); project-level exploration stays with `/hv-vision`. The artifact lands at `.hv/designs/<ID>.md` and feeds `/hv-plan` as soft input — never required.
## Step 1 — Preflight
```bash
.hv/bin/hv-preflight
```
See `docs/reference/preflight.md` for exit-code handling.
**Autonomy gate.** Read `autonomy.level` and parse the `--auto-loop` flag:
```bash
LEVEL=$(jq -r '.autonomy.level // "off"' .hv/config.json)
```
Also parse `AUTO_LOOP`: scan `$ARGUMENTS` (the skill `args` value) for the literal string `--auto-loop`; set `AUTO_LOOP=true` if present, `AUTO_LOOP=false` otherwise. Then branch:
- **`LEVEL == "loop"` AND `AUTO_LOOP=false`** — print *"Note: /hv-brainstorm is skipped under loop autonomy (throughput mode). Re-run with `/hv-config` set to off or