prd/create

Creating a PRD from scratch using the BMAD method involves a 12-step interactive workflow that guides product teams through discovery, vision, success criteria, and functional requirements with user approval at each stage to ensure cross-functional alignment.

The BMAD methodology for product requirements documentation is a structured, collaborative approach that systematically builds a PRD by defining user journeys, domain considerations, and functional requirements to deliver a high-density capability contract.

To structure functional and non-functional requirements in a PRD, follow a guided workflow that scopes project-type requirements, success criteria, and domain considerations, ensuring all sections align with validation and phased development plans.

Yes, you can track PRD workflow progress and audit reviews during creation by utilizing frontmatter-based workflow state tracking, which maintains progress visibility and supports repeatable cross-functional reviews throughout the 12-step process.

The best way to align product vision with phased development plans is to use a step-by-step PRD construction process that explicitly maps innovation insights and domain requirements to risk validation and phased delivery schedules.

Guided PRD creation effectively defines user journeys and success criteria by walking product teams through an interactive discovery process, capturing high-density capability contracts that align with specific project-type and domain requirements.