Use vertical slices (tracer bullets) to split the plan into independently claimable issue tracker issues.
The issue tracker and triage label vocabulary should already have been provided to you; if not, run /setup-matt-pocock-skills。
Process
1. Gather context
Work from what is already in the conversation context. If the user passes an issue reference (issue number, URL, or path) as an argument, fetch it from the issue tracker and read the full body and comments.
2. Explore the codebase (optional)
If you have not yet explored the codebase, explore it first to understand the current state of the code. Issue titles and descriptions should use the project domain glossary vocabulary and comply with relevant ADRs.
3. Draft vertical slices
Split the plan into tracer bullet issues. Each issue is a thin vertical slice that goes end-to-end through all integration layers, not a horizontal slice of a single layer.
Slices can be HITL or AFK. HITL slices require human interaction, such as an architecture decision or design review. AFK slices can be implemented and merged without human interaction. Prefer AFK whenever possible.
4. Quiz the user
Present the proposed breakdown as a numbered list. For each slice show:
- Title: short descriptive name
- Type:HITL / AFK
- Blocked by: which other slices must be completed first (if any)
- User stories covered: which user stories it covers (if any are in the source material)
Ask the user:
- Is the granularity appropriate? (too coarse / too fine)
- Are the dependency relationships correct?
- Do any slices need to be merged or split further?
- Are the HITL and AFK markings correct?
Iterate until the user approves the breakdown.
5. Publish the issues to the issue tracker
For each approved slice, publish a new issue to the issue tracker. Use the issue body template below. These issues are considered ready for AFK agents to pick up; unless otherwise instructed, apply the correct triage label when publishing.
Publish issues in dependency order (blockers first), so that real issue identifiers can be referenced in the "Blocked by" field.
A reference to the parent issue in the issue tracker (if the source is an existing issue; otherwise omit this section).
What to build
A concise description of this vertical slice. Describe the end-to-end behavior, not a layer-by-layer implementation.
Avoid concrete file paths or code snippets; they go stale quickly. 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 here with a brief note that it came from the prototype. Keep the decision-dense parts, not a full working demo.
Acceptance criteria
- Criterion 1
- Criterion 2
- Criterion 3
Blocked by
- A reference to the blocking issue (if any)
If there is no blocker, write "None - can start immediately".
Do not close or modify any parent issue.