to-tickets

Pass the spec path, issue number, or URL as an argument, or work from the current conversation. The skill drafts vertical tracer-bullet slices, shows each ticket's title, blockers, and delivered behavior, then iterates with you until you approve the breakdown.

A vertical slice cuts a narrow but complete path through every layer (schema, API, UI, tests) rather than a horizontal slice of one layer. Each completed slice is demoable or verifiable on its own and sized to fit in a single fresh context window.

Yes, the skill publishes one issue per ticket in dependency order using the tracker's native blocking or sub-issue relationships, applying the ready-for-agent triage label. Without a real tracker, it writes one markdown file per ticket under .scratch/<feature-slug>/issues/.

Each ticket declares the tickets that must complete before it can start. On real trackers these become native blocking links referencing real issue identifiers; locally they are written as text in each ticket file's Blocked by section.

Wide refactors are sequenced as expand-contract: add the new form beside the old, migrate call sites in blast-radius-sized batches each as its own ticket, then delete the old form in a final ticket blocked by every migration batch.

The issue tracker and triage label vocabulary must be provided beforehand by running /setup-matt-pocock-skills. Without that configuration the skill cannot know where to publish tickets or which labels to apply.