wave-createlisted

# wave-create Materialize one approved wave from a slug and a set of chosen issue ids (the human picked them via `wave-plan`): assemble the roster, run DoR + cross-wave, render the durable `WAVE.md` spine, create sidecar dirs, and set the `queued` soft-claim on each issue. **Does not dispatch** — that is `wave-start` (P7.4). **Does not author the `WAVE.md` markdown** — the engine `renderSpine`/`spine create` owns every parser-consumed section (ADR-0016); this skill supplies only the structured inputs and the opaque `## DOR-check` prose. Your job is the **judgment** — assembling the roster, deciding whether DoR failures and cross-wave conflicts warrant proceeding or aborting, composing the payload, and setting the soft-claim in the right order. The CLI plumbing (the full worked sequence, the exact payload shape, a worked `payload.json`) lives in [reference/create-mechanics.md](reference/create-mechanics.md) — reach for it once the gate checks pass. You never write a tracker directly; everything goes through the engine CLI (`{{wave-cli}}`). ## When to Use - The human has approved a set of issue ids from `wave-plan` and is ready to materialize the wave. - You have a slug (e.g. `2026-06-18-triage-engine`) and a list of ids. Do **not** use this for planning (that is `wave-plan`), for slicing work into issues (`to-issues`), or for dispatching workers (`wave-start`). wave-create is the materialization step; wave-plan is the advisory pass that precedes it. ## THE FLOTILLA BOUND