bmad-create-product-brief

To turn vague product ideas into a structured product brief, this Skill guides teams through a stepwise workflow covering problem definition, users, metrics, and MVP scope with menu-driven confirmation and template-based artifact generation.

You can build a product brief collaboratively across sessions using frontmatter-driven state tracking that preserves stepsCompleted and inputDocuments, ensuring consistent and auditable documentation from brainstorming to final MVP scope.

The best way to align stakeholders during early-stage product discovery is to use a guided, stepwise workflow that integrates research and project context into a collaboratively built product brief, accelerating decision-making.

Yes, you can integrate brainstorming, research, and project context inputs to seed the product brief, which progressively fills a template-based artifact (product-brief.template.md) with your collaborative decisions.

Yes, the product brief workflow enforces menu-driven continuation and validation to ensure explicit user confirmation before moving forward, preserving workflow state and preventing undocumented scope changes.

When defining MVP scope and metrics, the template-based product brief requires strict adherence to its stepwise workflow and frontmatter state tracking, limiting rapid ad-hoc edits outside the guided menu-driven process.