Files
BMAD-METHOD/docs/how-to/workflows/create-product-brief.md
forcetrainer e535f94325 docs: comprehensive style guide update with reference and glossary standards
Style Guide Additions:
- Add Reference Structure section with 6 document types (Index, Catalog,
  Deep-Dive, Configuration, Glossary, Comprehensive)
- Add Glossary Structure section with table-based format leveraging
  Starlight's right-nav for navigation
- Include checklists for both new document types

Reference Docs Updated:
- agents/index.md: Catalog format, universal commands tip admonition
- configuration/core-tasks.md: Configuration format with admonitions
- configuration/global-config.md: Table-based config reference
- workflows/index.md: Minimal index format
- workflows/core-workflows.md: Catalog format
- workflows/document-project.md: Deep-dive with Quick Facts admonition
- workflows/bmgd-workflows.md: Comprehensive format, removed ~30 hr rules

Glossary Rewritten:
- Converted from 373 lines with ### headers to 123 lines with tables
- Right nav now shows 9 categories instead of 50+ terms
- Added italic context markers (*BMGD.*, *Brownfield.*, etc.)
- Alphabetized terms within categories
- Removed redundant inline TOC

All Docs:
- Remove horizontal rules (---) per style guide
- Remove "Related" sections (sidebar handles navigation)
- Standardize admonition usage
- Archive deleted workflow customization docs

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2026-01-12 00:23:05 -05:00

2.4 KiB

title, description
title description
How to Create a Product Brief How to create a product brief using the BMad Method

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

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

:::note[Prerequisites]

  • BMad Method installed
  • Analyst agent available
  • Optional: Research documents from previous workflows :::

Steps

1. Load the Analyst Agent

Start a fresh chat and load the Analyst agent.

2. Run the Product Brief Workflow

*product-brief

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

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

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

The product brief feeds directly into the PRD workflow:

Analysis Output Planning Input
product-brief.md prd workflow
market-research.md prd context
technical-research.md architecture (Phase 3)

Planning workflows automatically load the product brief if it exists.

Common Patterns

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):

→ Phase 2: prd or tech-spec directly

Tips

  • Be specific about the problem — Vague problems lead to vague solutions
  • Ruthlessly prioritize MVP scope — Less is more
  • Document assumptions and risks — Surface unknowns early
  • Use research findings as evidence — Back up claims with data
  • Recommended for greenfield projects — Sets strategic foundation