to-tickets splits a plan, spec or conversation into vertical-slice tickets. Each slice cuts a narrow but complete path through every layer, can be verified on its own, and fits in one fresh context window. Each ticket names the tickets that block it.
The breakdown is presented as a numbered list for you to approve before anything is published.
What You Get
- A set of tickets that each deliver demoable end-to-end behaviour
- Blocking edges so you can see which tickets can start immediately
- Acceptance criteria as a checklist per ticket
- Expand-contract sequencing for wide refactors
Common Use Cases
- Turn a spec into work an agent can pick up ticket by ticket
- Plan a column rename or shared type change as expand, migrate and contract tickets
- Create local ticket files for a solo project with no remote tracker
What Makes It Unique
It treats blocking edges as first-class and publishes in dependency order so edges can reference real identifiers. Wide refactors get expand-contract batches, which keep CI green where a single vertical slice could not land. It also looks for prefactoring opportunities and quizzes you on granularity before publishing.
Under The Hood
A single SKILL.md with two embedded templates, one for local ticket files and one for tracker issues. It fetches an issue or spec you point to, explores the codebase, and publishes through whichever tracker setup-matt-pocock-skills configured. It marks tickets ready-for-agent and leaves any parent issue unchanged.