Spec to Tickets
By Alex Brown · Published · Updated
Slices a spec into thin end-to-end tickets with blocking links, each one demoable on its own rather than a layer-by-layer task list.
Tags: product, productivity
Prompt template
## Spec to Tickets Break this spec into tickets. - The spec: [textarea: Paste the spec] - Team and stack: [text: Who builds it and with what] - Ticket tracker format: [dropdown: Plain markdown, GitHub issues, Linear style] - Target ticket size: [dropdown: Under a day, One to two days, Up to a week] - Existing work to build on: [textarea: Code or tickets already in place] Slice vertically as tracer bullets: the first ticket is the thinnest path that runs end to end through every layer, even if crude, so the riskiest integration is proven early. Each later ticket widens that path with one behavior. Never split by layer such as database, then API, then interface, since none of those can be demoed alone. Every ticket needs a title, the user-visible outcome, a demo line saying how to show it working, acceptance criteria drawn from the spec, size, and a blocked-by list. Draw the blocking edges so independent tickets can run in parallel, and name any ticket that blocks the most others. Finish with a suggested order and a note on what the spec leaves unspecified.