decompose-prd

PRD decomposition extracts functional and non-functional requirements and maps them into phase-aligned atomic task specifications using a fixed framework, producing stable TASK identifiers and a batch execution runbook for deterministic pipelines.

PRD decomposition handles phase-based planning by reading the document, extracting requirement mappings, and organizing the output into phase-task artifacts that enable predictable, structured execution across project milestones.

The best way to generate a batch execution runbook from a PRD is to use a decomposition framework that produces an _index.md file containing phase-aligned task specs with strict naming conventions for reproducible execution.

You need a PRD containing identifiable functional and non-functional requirements to feed the decomposition framework, which reads the document and translates those high-level goals into concrete work items.

You should avoid fixed decomposition frameworks for task spec generation when a project lacks clear phase-based planning requirements or when the PRD does not contain identifiable functional and non-functional requirement mappings.