1---
2name: to-issues
3description: Break a plan, spec, or PRD into independently-grabbable GitHub issues using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.
4---
5 
6# To Issues
7 
8Break a plan into independently-grabbable GitHub issues using vertical slices (tracer bullets).
9 
10## Process
11 
12### 1. Gather context
13 
14Work from whatever is already in the conversation context. If the user passes a GitHub issue number or URL as an argument, fetch it with `gh issue view <number>` (with comments).
15 
16### 2. Explore the codebase (optional)
17 
18If you have not already explored the codebase, do so to understand the current state of the code.
19 
20### 3. Draft vertical slices
21 
22Break the plan into **tracer bullet** issues. Each issue is a thin vertical slice that cuts through ALL integration layers end-to-end, NOT a horizontal slice of one layer.
23 
24Slices may be 'HITL' or 'AFK'. HITL slices require human interaction, such as an architectural decision or a design review. AFK slices can be implemented and merged without human interaction. Prefer AFK over HITL where possible.
25 
26<vertical-slice-rules>
27- Each slice delivers a narrow but COMPLETE path through every layer (schema, API, UI, tests)
28- A completed slice is demoable or verifiable on its own
29- Prefer many thin slices over few thick ones
30</vertical-slice-rules>
31 
32### 4. Quiz the user
33 
34Present the proposed breakdown as a numbered list. For each slice, show:
35 
36- **Title**: short descriptive name
37- **Type**: HITL / AFK
38- **Blocked by**: which other slices (if any) must complete first
39- **User stories covered**: which user stories this addresses (if the source material has them)
40 
41Ask the user:
42 
43- Does the granularity feel right? (too coarse / too fine)
44- Are the dependency relationships correct?
45- Should any slices be merged or split further?
46- Are the correct slices marked as HITL and AFK?
47 
48Iterate until the user approves the breakdown.
49 
50### 5. Create the GitHub issues
51 
52For each approved slice, create a GitHub issue using `gh issue create`. Use the issue body template below.
53 
54Create issues in dependency order (blockers first) so you can reference real issue numbers in the "Blocked by" field.
55 
56<issue-template>
57## Parent
58 
59#<parent-issue-number> (if the source was a GitHub issue, otherwise omit this section)
60 
61## What to build
62 
63A concise description of this vertical slice. Describe the end-to-end behavior, not layer-by-layer implementation.
64 
65## Acceptance criteria
66 
67- [ ] Criterion 1
68- [ ] Criterion 2
69- [ ] Criterion 3
70 
71## Blocked by
72 
73- Blocked by #<issue-number> (if any)
74 
75Or "None - can start immediately" if no blockers.
76 
77</issue-template>
78 
79Do NOT close or modify any parent issue.
80