bmad-create-prd

A product requirements document is generated end-to-end by guiding structured product discovery and auto-assembling sections like Executive Summary, User Journeys, and Functional Requirements into a single coherent, traceable file.

An end-to-end PRD workflow yields sections such as Executive Summary, Success Criteria, User Journeys, Domain Requirements, Innovation, Project-Type Requirements, and both Functional and Non-Functional Requirements.

Yes, you can generate product requirements for brownfield projects. The workflow loads input documents from common sources, applies a capability contract, and surfaces gaps for discussion before producing the final document.

Traceability in product requirements is enforced through frontmatter-tracked steps and loaded input documents. This ensures every section documented during the discovery workflow remains linked to its source context.

The best way to manage collaborative product discovery is using a step-file driven workflow. It provides collaborative prompts and checks that align with product differentiators to auto-assemble documentation coherently.

Input documents are loaded from common sources to support both greenfield and brownfield projects during PRD creation. If gaps exist, the guided discovery steps surface them for collaborative discussion before finalizing requirements.