to-ticketslisted

Split a slice-ready spec from /to-spec into independent vertical-slice work-units for a large ticket, then render an approval board and STOP. Each slice is a thin COMPLETE path through every layer of the chain it needs, verifiable on its own testing seam. Writes one work-unit per slice under handoffs/<TICKET-ID>/slices/ plus a slice-board.md carrying the dependency waves and a DAG, for you to accept or edit. Internal work-units only — it never writes to the tracker. Runs inside the /start-ticket DECOMPOSE path, after /to-spec and before the orchestrator dispatches any slice.
konstantinos-malavazos/claude-code-playbook · ★ 2 · AI & Automation · score 68

Install: claude install-skill konstantinos-malavazos/claude-code-playbook

# to-tickets — spec → vertical slices + approval board > Prior art: Matt Pocock's `to-tickets` skill (MIT), upstream-renamed from `to-issues`. This > is an adaptation, not a copy. Two differences: the slices are internal work-units rather > than issues published to a tracker — one `<TICKET-ID>` stays one ticket, and these files > are only how the work beneath it is parallelised; and the interactive granularity > interview is replaced by a board you approve or edit. ## When this runs Only in the `/start-ticket` **decompose path** — the planner set `slice-count > 1` — after `/to-spec` has written `slice-spec.md`. [docs/shared/09](../../../docs/shared/09-decompose-path.md) is the whole path. ## Inputs - `<workspace>/.claude/handoffs/<TICKET-ID>/slice-spec.md` — behaviours and testing seams. Primary. - `<workspace>/.claude/handoffs/<TICKET-ID>/planner.md` — layer allocation, repos and files per behaviour, and `## Open questions for grilling`. - What the **grilling gate** settled: every question is answered, or deferred with an owner and a price. The price drives the lanes below. ## What a slice is A **thin, complete, vertical** path. It goes through every layer of the repo's chain that the behaviour needs — in the order `## The layer chain` in that repo's `CLAUDE.md` states — and it is verifiable on its own, by its seam from the spec. **A single layer is not a slice.** "The schema part" proves nothing, because a schema with no consumer has no observable result to de