Break a PRD into independently-grabbable tasks using tracer-bullet vertical slices. Use when user wants to convert a PRD to tasks, create implementation tickets, or break down a PRD into work items.
Break a PRD into independently-grabbable tasks using vertical slices (tracer bullets).
This skill defines the implementation tasks for a slice and should also include slice closeout work.
Ask the user for the PRD file.
If the PRD is not already in your context window, read it.
If you have not already explored the codebase, do so to understand the current state of the code.
Break the PRD into tracer bullet tasks. Each task is a thin vertical slice that cuts through ALL integration layers end-to-end, NOT a horizontal slice of one layer.
<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>Present the proposed breakdown as a numbered list. For each slice, show:
Ask the user:
Iterate until the user approves the breakdown.
The tasks should live in a file in a path like docs/slices/*feature*/TASKS.md.
Create tasks in dependency order (blockers first) so you can reference real tasks numbers in the "Blocked by" field.
Always include a final slice-closeout task that runs an architecture review after the implementation tasks are complete.
That closeout task should:
improve-codebase-architecture on the completed sliceTASKS.md file or as ADR updates when appropriateA 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: