To Tickets (ex To Issues, Claude Code skill)
Breaks a plan, spec or PRD into independently shippable GitHub issues. Not by horizontal layers (front, back, DB) but by vertical slices, 'tracer bullets' that cut through all layers end-to-end. Each issue is demoable on its own. The skill asks if the granularity is right, marks each slice HITL (human-in-the-loop) or AFK (away-from-keyboard), resolves dependencies, then publishes in order, blockers first, so it can reference real issue IDs in the 'Blocked by' field. Applies the `needs-triage` label to each issue.
Strengths
- Vertical tracer-bullet by default, each issue is demoable and mergeable on its own
- Marks HITL/AFK explicitly, you know from the breakdown which issues need human review
- Publishes in dependency order with real issue IDs in the 'Blocked by' field
- 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
- No formal dry-run, either you review and publish, or nothing (it applies directly after validation)
- Tracer-bullet slicing imposes strong discipline, not suited to strictly layered specs
Best for
- Tech leads coming out of planning with a PRD who want to avoid 3h of manual breakdown
- PM/PO who want their specs to become actionable issues without going through a dev
- Teams practising continuous shipping who prefer 8 thin issues over 2 thick ones