Break a plan, spec, or conversation into a set of tickets: tracer-bullet vertical slices, each ticket declaring block its tickets.
The issue tracker and triage label vocabulary should already be provided; if not, ask the user to run /setup-matt-pocock-skills。
Process
1. Gather context
Use what already exists in the conversation context. If the user passes a reference (spec path, issue number, or URL) as an argument, fetch and fully read its body and comments.
2. Explore the codebase (optional)
If you have not explored the codebase yet, first understand the current state of the code. Ticket titles and descriptions should use the project domain glossary vocabulary and comply with relevant ADRs.
Look for prefactor code, opportunities to make implementation easier. “Make the change easy, then make the easy change.”
3. Draft vertical slices
Break the work into tracer bullet tickets。
- Each slice must cut through every layer (schema, API, UI, tests) to form a narrow but complete path; it must be a vertical slice, not a horizontal slice of one layer
- A completed slice can be demoed or verified independently
- Each slice must be small enough to fit in one fresh context window
- Any prefactoring should be completed first
For each ticket, provide blocking edges: other tickets that must be completed before it starts. Tickets with no blockers can start immediately.
Wide refactors are the exception to vertical slicing. Wide refactor is a mechanical change affecting the entire codebase, such as renaming a column or retyping a shared symbol; a single edit would break thousands of call sites, making it impossible for any vertical slice to stay green independently. Do not force it into a tracer bullet; order it by expand–contract . First expand: add the new form alongside the old form and keep everything working. Then migrate call sites in batches by blast radius (by package, directory, etc.), with one ticket per batch, blocked by the expand; the old form still exists, so CI stays green for each batch. Finally contract: once no callers remain, remove the old form in a ticket blocked by all migrate batches. If even individual batches cannot stay green, still keep this sequence, but have them share an integration branch, and have them all block the final integrate-and-verify ticket; only promise green at the end.
4. Quickly confirm with the user
Present the proposed breakdown as a numbered list. Each ticket includes:
- Title: a short descriptive name
- Blocked by: other tickets that must be completed first (if any)
- What it delivers: the end-to-end behaviour this ticket delivers
Ask the user:
- Is the granularity appropriate (too coarse or too fine)?
- Are the blocking edges correct, and does each ticket depend only on the tickets that truly gate it?
- Should any tickets be merged or split further?
Iterate until the user approves the breakdown.
5. Publish the tickets to the configured tracker
Publish the approved tickets. The specific method depends on /setup-matt-pocock-skills configured tracker; the tickets are the same, only the shape of the blocking edges differs:
- Local files → under
.scratch/<feature-slug>/issues/<NN>-<slug>.mdwrite one file per ticket, numbered in dependency order (blockers first) starting from01. Each file's "Blocked by" lists the number/title it depends on. Use the per-ticket template below; put only one ticket in each file, never write it as one combined file. - real issue tracker (GitHub, Linear, etc.) → publish one issue per ticket in dependency order (blockers first), so that blocking edges can reference real identifiers. When the platform supports it, use a native blocking/sub-issue relationship; otherwise write the blocking issues into each ticket's "Blocked by". Unless otherwise instructed, apply the
ready-for-agenttriage label; these tickets are naturally claimable by an agent.
Process the frontier: tickets for which all blockers are complete. A purely linear chain is top to bottom.
Do not close or modify any parent issue.
:What to build: the end-to-end behaviour this ticket delivers from the user's perspective, not a layer-by-layer implementation list.
Blocked by: gate this ticket's numbers/titles, or "None (can start immediately)".
Status: ready-for-agent
- Acceptance criterion 1
- Acceptance criterion 2
Parent
Reference to the parent issue on the Tracker (if the source is an existing issue; otherwise omit this section).
What to build
the end-to-end behaviour this ticket delivers from the user's perspective, not a layer-by-layer implementation.
Acceptance criteria
- Criterion 1
- Criterion 2
Blocked by
- Reference to each blocking ticket, or "None (can start immediately)".
In either form, avoid specific file paths or code snippets; they quickly become outdated. Exception: if a snippet produced by the prototype encodes a decision more precisely than prose (state machine, reducer, schema, type shape), you may inline it, with a brief note that it comes from the prototype. Keep only the decision-rich parts, and do not include a working demo.