bmad-product-brief

To create a product brief from rough notes, use guided discovery to extract core requirements. It processes brain dumps and transcripts into a structured, review-ready document with YAML frontmatter, ensuring no critical decisions are missed.

Updating an existing product brief requires change reconciliation to surface conflicts and validate updates against the original purpose. This workflow tracks decisions and applies addenda to maintain context accuracy without inflating assumptions.

Product brief validation during coaching works by checking your draft against its own purpose through structured discovery. It surfaces missing decisions and hidden assumptions, transforming rough ideas into honest, right-sized product briefs.

Yes, you can use decision logs to reconcile changes in a product brief. The system tracks decisions and integrates addenda, ensuring that updates preserve historical context and produce review-ready documents for downstream planning.

Yes, YAML frontmatter is required for product brief drafting. It structures the document metadata, enabling the system to parse drafts, apply addenda, and maintain decision-log tracking for accurate change reconciliation.

When product brief discovery hits missing decisions, a product manager should use guided coaching to surface those gaps. The system highlights assumptions, prompts for clarification, and logs decisions to maintain a review-ready brief.