Prd To Issues

Break a PRD into independently-grabbable GitHub issues using vertical slices (tracer bullets).

## Process

### 1. Locate the PRD

Ask the user for the PRD GitHub issue number (or URL).

If the PRD is not already in your context window, fetch it with `gh issue view <number>` (with comments).

### 2. Explore the codebase (optional)

If you have not already explored the codebase, do so to understand the current state of the code.

### 3. Draft vertical slices

Break the PRD 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.

Slices 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.

<vertical-slice-rules>
- Each slice delivers a narrow but COMPLETE path through every layer (schema, API, UI, tests)
- A completed slice is demoable or verifiable on its own
- Prefer many thin slices over few thick ones
</vertical-slice-rules>

### 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 (if any) must complete first
- **User stories covered**: which user stories from the PRD this addresses

Ask the user:

- Does the granularity feel right? (too coarse / too fine)
- Are the dependency relationships correct?
- Should any slices be merged or split further?
- Are the correct slices marked as HITL and AFK?

Iterate until the user approves the breakdown.

### 5. Create the GitHub issues

For each approved slice, create a GitHub issue using `gh issue create`. Use the issue body template below.

Create issues in dependency order (blockers first) so you can reference real issue numbers in the "Blocked by" field.

<issue-template>
## Parent PRD

#<prd-issue-number>

## Design Reference

- **Parent design page:** `<Figma URL of the full design page from the PRD>`
- **Relevant node:** `<Figma URL with node-id for the specific section relevant to this slice>` (if applicable)

If the slice has no UI, write "No UI in this slice." Do NOT embed screenshots — use the Figma links as the living reference.

## What to build

A concise description of this vertical slice. Describe the end-to-end behavior, not layer-by-layer implementation. Reference specific sections of the parent PRD rather than duplicating content.

## Acceptance criteria

- [ ] Criterion 1
- [ ] Criterion 2
- [ ] Criterion 3

## Blocked by

- Blocked by #<issue-number> (if any)

Or "None - can start immediately" if no blockers.

## User stories addressed

Reference by number from the parent PRD:

- User story 3
- User story 7

</issue-template>

### 6. Create architecture review issue

After all feature slices are created, add one final issue: an architecture review that runs `/improve-codebase-architecture` after all feature slices are complete. This issue is blocked by ALL other slices and ensures structural health is checked after every PRD is shipped.

Use this template:

Parent PRD

#

What to do

Run /improve-codebase-architecture to check whether the work from this PRD introduced architectural friction:

• Shallow modules that should be deepened
• Tightly-coupled seams between new and existing code
• Opportunities to improve testability at module boundaries

This is a post-implementation review, not a blocker for shipping.

Blocked by

• Blocked by #

### 6. Link sub-issues to the parent PRD

After all issues are created, link each one as a **sub-issue** of the parent PRD issue using the `sub_issue_write` MCP tool (method: `add`). This makes the PRD act as an epic with a trackable checklist of child issues.

Do NOT close or modify the parent PRD issue.

$ARGUMENTS