to-issueslisted

# To Issues Break a plan into independently-grabbable issues using vertical slices (tracer bullets). **Not this skill** — use [`to-prd`](../to-prd/SKILL.md) in defer mode when the user wants to *park* a single surfaced lead (one issue + one roadmap paragraph). `to-issues` is for shattering an already-planned chunk of work into N tickets ready to execute. Defer mode pushes work OUT of now; `to-issues` decomposes work INTO actionable slices. The issue tracker and triage label vocabulary should have been provided to you — run `/setup-matt-pocock-skills` if not. Issue titles, branch names, and commit messages follow the [git-hygiene rule](../../../standards/rules/git-hygiene.mini.md). Default branch prefix per type: AFK + feature → `feat/`, AFK + bug → `fix/`, HITL → ask first. ## Second-dev cold-pickup rule Every issue this skill produces must contain enough context that a **second dev** — teammate, AFK agent, or returning maintainer — who has never seen the conversation can act on it cold. Each issue gets a parent reference, a behavioral *what to build* description, inline machine-checkable acceptance criteria, and an explicit *blocked by* list. The issue body is the contract surface; conversation context is not. Rationale: ai-kit defaults assume ≥2 devs (one writer, one reviewer), per ai-kit issue #52. The to-issues template enforces this structure — never emit an issue that drops acceptance criteria or the parent pointer. If a slice cannot be specified cold from curren