bmad-product-brief

To create an executive product brief, you need structured discovery to synthesize project artifacts and web research into a decision-ready narrative. The workflow stages intent understanding, contextual discovery, elicitation, draft-and-review, and finalization with artifact outputs.

Updating an existing product brief involves detecting the update intent and routing to contextual discovery, scanning new project documents for signals, and supplementing gaps with competitive research. Multiple reviewer lenses then surface critical gaps before presenting the finalized brief.

Product discovery for a brief works by scanning your project documents for relevant signals and supplementing gaps with competitive or market research. This contextual artifact and web research feeds into a guided elicitation and draft-review process.

You can generate a PRD-ready output by producing an optional LLM distillate pack from the product brief. This token-efficient detail pack contains overflow context like requirements hints, rejected ideas, technical and competitive details for downstream PRD creation.

You need to provide YAML frontmatter-driven discovery fields to enable product brief synthesis. The workflow then uses these fields alongside your project artifacts and web research to stage intent understanding and contextual discovery.

Autonomous product briefing workflows still require YAML frontmatter-driven discovery fields and run through draft-review quality gates with multiple reviewer lenses. These gates intentionally surface untested assumptions and critical gaps before finalizing the executive brief.