PRD to Issues

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

Process

1. Locate the PRD

Ask the user for the PRD Linear issue identifier (e.g. TEAM-123).

If the PRD is not already in your context window, fetch it using the Linear MCP get_issue tool.

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.

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?
• Which Linear team should the issues be created in?

Iterate until the user approves the breakdown.

5. Create the Linear issues

For each approved slice, create a Linear issue using the Linear MCP save_issue tool (title, description, team). Use the issue body template below.

Create issues in dependency order (blockers first) so you can reference real Linear identifiers in the blockedBy and relatedTo fields.

• Set relatedTo: [<prd-issue-id>] on every child issue to link back to the parent PRD
• Set blockedBy: [<issue-id>, ...] to express intra-slice dependencies using Linear's native relations

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

User stories addressed

Reference by number from the parent PRD:

• User story 3
• User story 7

Do NOT close or modify the parent PRD issue.