PRD to implementation

Checks a PRD for engineering readiness with a PM review, breaks it into epics and stories, gets engineering sign-off, then files the tickets and submits each story as its own implementation request.

Template	prd-decomposition
Works on	A git repository, cloned into an isolated Docker sandbox
Where a person acts	PM Review: PRD Readiness Analysis — a person reviews and annotates, waiting up to 7d Engineering Review: Approve Decomposition — a person reviews and annotates, waiting up to 7d

The workflow

Drawn from the template spec at build time. Bookkeeping nodes that only record status are left out; amber nodes are where a person acts.

flowchart TD
  n_analyzePrd["Analyze PRD"]
  n_pmReview>"PM Review: PRD Readiness Analysis<br/><small>person: review</small>"]
  n_decomposePrd["Decompose PRD"]
  n_engReview>"Engineering Review: Approve Decomposition<br/><small>person: review</small>"]
  n_createTrackerItems["Create tracker items"]
  n_terminateTimeout(["Timed out<br/><small>timeout</small>"])
  n_submitPrdWorkRequests["Submit PRD work requests"]
  n_done(["Done"])
  n_analyzePrd --> n_pmReview
  n_pmReview -->|"submitted"| n_decomposePrd
  n_pmReview -->|"timed out"| n_decomposePrd
  n_decomposePrd --> n_engReview
  n_engReview -->|"submitted"| n_createTrackerItems
  n_engReview -->|"timed out"| n_terminateTimeout
  n_createTrackerItems --> n_submitPrdWorkRequests
  n_submitPrdWorkRequests --> n_done
  class n_pmReview,n_engReview gate

Maturity: seeded, not yet proven

Seeded content rather than a proven flow. The connector, the agents, and the governance it relies on exist, but only the engineering flow has a complete, exercised end-to-end path today. See product overview §8.

Use it

Every built-in template is seeded into the workflow library and can be cloned, edited on the visual canvas, and versioned — see architecture for the node types. The spec lives in packages/shared/src/workflow/templates/prdDecomposition.ts.