bmad-create-prd

To create a product requirements document, use a structured, multi-step workflow that guides you through defining product vision, success criteria, user journeys, and functional scope. It acts as a facilitator to systematically capture all critical product aspects.

Comprehensive product requirements documentation should include the product vision, success criteria, user journeys, functional and non-functional requirements, and project scope to ensure clear communication for downstream development and design processes.

To define functional and non-functional requirements, follow a guided discovery process that helps you document specific user journeys, system behaviors, and project scope, ensuring all constraints and feature capabilities are captured for development.

The best way to structure PRDs for development teams is to use a disciplined, step-by-step workflow that clearly separates product vision, success criteria, and scope from detailed functional and non-functional requirements.

Yes, you can use this structured workflow to document requirements for an existing product update by systematically defining the new vision, updated user journeys, and modified scope for the downstream design and development processes.