bmad-create-prd

To generate a complete PRD from scattered notes, this Skill guides discovery through a stepwise workflow, classifying your input and populating a structured document with sections like Executive Summary, User Journeys, and Functional Requirements.

A structured product requirements document for engineering should include Success Criteria, Domain Requirements, Innovation, Project-Type Requirements, and both Functional and Non-Functional Requirements to ensure downstream architecture and engineering work is fully guided.

Validating requirements with traceability involves guiding discovery through a stepwise workflow to classify inputs, ensuring every functional and non-functional requirement in your PRD is referenceable and verifiable against original user needs.

Yes, you can use conversation context and input documents to populate a structured product management document. The stepwise workflow facilitates discovery and scoping to build a verifiable PRD from your provided context.

The best way to scope project-type requirements and user journeys is to use a guided discovery workflow that classifies inputs and outputs a structured PRD, ensuring all requirements are referenceable for downstream architecture, UX, and engineering work.

PRD generation fails to support downstream tasks when it lacks structured sections like Domain Requirements and Non-Functional Requirements. This Skill ensures outputs are referenceable and verifiable to directly support architecture, UX, and engineering work.