To Tickets (ex To Issues, Claude Code skill)
Breaks a plan, spec or the conversation into independently shippable 'tracer bullet' tickets. The command is now /to-tickets (former name: /to-issues). Not by horizontal layers (front, back, database) but by vertical slices that cut through every layer end to end, each demoable on its own and sized to fit one context window. The skill has you validate granularity and blocking edges before publishing, then publishes in order, blockers first: as local files (`.scratch/<feature>/issues/`) or in your tracker, with real blocking relationships and the `ready-for-agent` label. A wide refactor follows the expand-contract sequence: new form next to the old one, call sites migrated in batches, then the old form deleted.
Strengths
- Vertical tracer-bullet by default, each ticket is demoable and mergeable on its own
- Two outputs to choose from: local files under `.scratch/` to reread first, or native tracker tickets
- Publishes in dependency order, with real blocking relationships in the tracker
- Interactive quiz: the skill asks you to validate granularity before pushing
Limitations
- Assumes your issue tracker is known and /setup-matt-pocock-skills has been run to provide the label vocabulary
- Tickets sized for one context window: on a large feature, the list grows fast
- Tracer-bullet slicing imposes strong discipline, not suited to strictly layered specs
Best for
- Tech leads coming out of scoping with a spec who want to avoid 3h of manual breakdown
- PM/PO who want their specs to become actionable tickets without going through a dev
- Teams shipping continuously who prefer 8 thin tickets over 2 thick ones