bmad-create-prd

This skill orchestrates a complete PRD creation workflow from initialization through discovery, scoping, and final polish, appending content sections to a single document for full governance and traceability.

The best way to facilitate PRD collaboration is using a guided workflow with a facilitator persona that preserves user voice and context while ensuring document sections map directly to downstream artifacts.

A stepwise product requirements document workflow uses frontmatter-driven state tracking to manage the assembly process, safely appending content to the PRD document as each step completes.

You do not need external tools to generate product requirements documentation; the workflow relies entirely on repository-provided templates and frontmatter-driven state to assemble the PRD.

Yes, you can use this guided workflow for scoping non-functional requirements, as the process explicitly includes dedicated steps for defining both functional requirements, non-functional requirements, and project type.

You should avoid an automated PRD generation workflow if your project lacks initial discovery context or input documents, as the process relies on gathering vision and journey context to populate downstream artifacts.