Break a PRD into independently-grabbable Linear issues using tracer-bullet vertical slices. Use when user wants to convert a PRD to Linear issues, create implementation tickets, or break down a PRD into work items in Linear.
Break a PRD into independently-grabbable Linear issues using vertical slices (tracer bullets).
Ask the user for the PRD Linear issue identifier (e.g. team prefix and number like ENG-123, or a URL).
If the PRD is not already in your context window, fetch it using the Linear MCP tools.
If you have not already explored the codebase, do so to understand the current state of the code.
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> <issue-template> ## Parent PRD </issue-template>Present the proposed breakdown as a numbered list. For each slice, show:
Ask the user:
Iterate until the user approves the breakdown.
For each approved slice, create a Linear issue using the Linear MCP tools. Ask the user which team to create issues in if not already known. Create issues in dependency order (blockers first) so you can reference real issue identifiers in the "Blocked by" field. Use Linear's blocking/blocked-by relations to link dependent issues.
Link to the parent PRD issue (e.g. ENG-123)
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.
Or "None - can start immediately" if no blockers.
Reference by number from the parent PRD:
Do NOT close or modify the parent PRD issue.