PRD-to-Task Breakdown
Assign an approved PRD and a PM agent proposes epics, vertical-slice stories, and tracer-bullet tasks — with splits, dependencies, and acceptance criteria — self-reviews them, and after your approval can publish the issues to your connected tracker.
Saves you ~2.9 h / run
How it works
- Trigger
- When you start the “Break down PRD” workflow.
- Job
- Read the PRD, propose the vertically-sliced breakdown.
- Outcome
- An implementation-ready task breakdown with dependencies.
What it installs
Agents 2
-
PM Agent
Proposes epics, stories, and tracer-bullet tasks from a PRD, self-reviews, and publishes after approval.
-
PRD-to-Task Breakdown Quality Reviewer
Checks primary evidence, domain controls, deliverable completeness, and communication quality, stopping the run when the work is wrong, unsupported, incomplete, or uncertain.
Teams 1
-
PRD-to-Task Breakdown quality team
The delivery agents produce the work while an independent quality reviewer checks each workflow handoff against explicit evidence, domain, and communication requirements before the run can continue.
Workflows 1
-
Break down PRD
Read the PRD, propose the vertically-sliced breakdown, self-review it, get approval, and publish the issues.
Skills 3
-
prd-to-issues
Break a PRD or plan into independently-grabbable issues as tracer-bullet vertical slices, each cutting through all layers end to end, present them for approval, then publish in dependency order. Adapted from mattpocock/skills/to-issues.
-
epic-breakdown-advisor
Break epics into vertical-slice stories using the Humanizing Work methodology: INVEST pre-validation, the 9 split patterns applied in order, and split evaluation for low-value work and equal sizing. Adapted from deanpeters/product-manager-skills/epic-breakdown-advisor.
-
user-story-splitting
Split a large story or epic into smaller, independently deliverable stories using systematic patterns (workflow, business rules, data, acceptance-criteria complexity, major effort, dependencies, devops, TADs) and validate each split. Adapted from deanpeters/product-manager-skills/user-story-splitting.
Requirements
- Connected issue tracker — Once you approve the breakdown, the agent can publish the epics, stories, and tasks as issues in your connected tracker, in dependency order. Until you connect it, the agent delivers the breakdown as a draft proposal from the PRD.
Setup guide
How to Break Down PRDs Into Tasks
A practical guide to turning approved PRDs into vertical slices, tracer-bullet tasks, dependencies, and issue proposals.
Read the setup guideDon't see your workflow? Describe it.
A sentence or two about a recurring job is enough. We design the playbook that runs it and show you exactly what it saves.