Skip to content
🤖 Consolidated, AI-optimized BMAD docs: llms-full.txt. Fetch this plain text file for complete context.
BMAD Logo BMAD Method

How to Create a Product Brief

Use the product-brief workflow to define product vision and strategy through an interactive process.

When to Use This

Section titled “When to Use This”
  • Starting new product or major feature initiative
  • Aligning stakeholders before detailed planning
  • Transitioning from exploration to strategy
  • Need executive-level product documentation

Prerequisites

Section titled “Prerequisites”
  • BMad Method installed
  • Analyst agent available
  • Optional: Research documents from previous workflows

Steps

Section titled “Steps”

1. Load the Analyst Agent

Section titled “1. Load the Analyst Agent”

Start a fresh chat and load the Analyst agent.

2. Run the Product Brief Workflow

Section titled “2. Run the Product Brief Workflow”
*product-brief

3. Answer the Interactive Questions

Section titled “3. Answer the Interactive Questions”

The workflow guides you through strategic product vision definition:

  • What problem are you solving?
  • Who are your target users?
  • What makes this solution different?
  • What’s the MVP scope?

4. Review and Refine

Section titled “4. Review and Refine”

The agent will draft sections and let you refine them interactively.

What You Get

Section titled “What You Get”

The product-brief.md document includes:

  • Executive summary - High-level overview
  • Problem statement - With evidence
  • Proposed solution - And differentiators
  • Target users - Segmented
  • MVP scope - Ruthlessly defined
  • Financial impact - And ROI
  • Strategic alignment - With business goals
  • Risks and open questions - Documented upfront

Integration with Other Workflows

Section titled “Integration with Other Workflows”

The product brief feeds directly into the PRD workflow:

Analysis OutputPlanning Input
product-brief.mdprd workflow
market-research.mdprd context
technical-research.mdarchitecture (Phase 3)

Planning workflows automatically load the product brief if it exists.

Common Patterns

Section titled “Common Patterns”

Greenfield Software (Full Analysis)

Section titled “Greenfield Software (Full Analysis)”
1. brainstorm-project - explore approaches
2. research (market/technical/domain) - validate viability
3. product-brief - capture strategic vision
4. → Phase 2: prd

Skip Analysis (Clear Requirements)

Section titled “Skip Analysis (Clear Requirements)”
→ Phase 2: prd or tech-spec directly

Tips

Section titled “Tips”
  • Be specific about the problem you’re solving
  • Ruthlessly prioritize MVP scope
  • Document assumptions and risks
  • Use research findings as evidence
  • This is recommended for greenfield projects
Section titled “Related”