bmad-create-prd

To create a product requirements document from scratch, use a structured facilitation workflow that guides you sequentially through product discovery, vision definition, scope planning, user journey mapping, and functional requirement drafting. This ensures all stakeholder context is captured before development begins.

Defining functional and non-functional requirements is best achieved through a guided workflow that enforces sequential execution and user confirmation at each step. This approach ensures requirements are measurable, traceable, and polished before architecture review.

Yes, you can use a PRD workflow for both new and existing products. Context-aware facilitation loads existing briefs, research, and project knowledge to support greenfield initiatives as well as brownfield product planning and requirement updates.

You can turn scattered notes into a complete PRD by using a workflow that performs document discovery and contextual loading. It ingests your raw research and stakeholder ideas, then guides you step-by-step to output a polished document ready for implementation planning.

Product discovery and scoping should include product vision definition, success criteria, and user journey mapping. Completing these sequential phases before drafting functional requirements prevents vague scoping and missing stakeholder context.

To ensure PRD completeness and quality, use a workflow with built-in guardrails that enforces measurable requirements, traceability, and document polishing. User-approved section generation at each sequential step guarantees a complete document before completion.