to-issueslisted

# to-issues Break a plan into independently-grabbable issues using **tracer-bullet vertical slices**, and write each with the wave **Header-Block** so a wave can grab it on creation. This is the linchpin of the pipeline: downstream `wave-create` / `wave-start` only ever see what this skill files. Your job is the **judgment** — slicing, classifying Risk/Worker, declaring Files, ordering the publish. The engine is the guardrail: it validates format, assigns ids, and runs the gates. So this skill stays on the judgment; the CLI invocation detail (commands, JSON shapes, the two-pass, the self-check) lives in [reference/filing-mechanics.md](reference/filing-mechanics.md) — reach for it once a breakdown is approved. You never write a tracker directly; everything goes through the engine CLI (`{{wave-cli}}`), which selects the configured store. Two modes: **create** (mint new issues from a plan) and **decorate** (add the missing wave fields to an issue someone already triaged). Decorate is not an alternative to `triage` — it is the second half of the same readiness. `triage` stamps the eligibility marker; this skill writes the planning header into the body, and only an issue carrying both is one the wave side can actually read. ## When to Use - The user has a plan, PRD, spec, or design doc and wants it turned into issues. - The user wants an already-triaged issue made **wave-readable** (decorate) — a `ready-for-agent` issue carries the eligibility marker but no planning header, s