bmad-create-product-brief

Generate a structured product brief through guided collaborative discovery.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/JingyiWng/databricks_ai_dev_kit_price_watcher --skill bmad-create-product-brief-jingyiwng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-create-product-brief
Source: https://github.com/JingyiWng/databricks_ai_dev_kit_price_watcher/tree/main/_bmad/bmm/workflows/1-analysis/bmad-create-product-brief
Command: npx skills add https://github.com/JingyiWng/databricks_ai_dev_kit_price_watcher --skill bmad-create-product-brief-jingyiwng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating a product brief often suffers from missing context, inconsistent structure, and lack of collaborative input, resulting in vague or incomplete documentation. This skill supplies a disciplined, step‑by‑step workflow that ensures every essential section—vision, users, metrics, and MVP scope—is captured collaboratively and consistently.

Core Features & Use Cases

  • Enforces sequential execution with step‑file architecture and frontmatter state tracking.
  • Detects existing workflow state to enable seamless continuation without data loss.
  • Presents interactive menus that pause for user input at each stage of discovery.
  • Generates a structured document from a template, automatically updating frontmatter.
  • Guides collaborative discovery of product vision, target users, success metrics, and MVP scope.
  • Provides final validation, status updates, and next‑step recommendations after completion.

Quick Start

Start the product brief workflow by saying, “let’s create a product brief.”

Frequently Asked Questions about bmad-create-product-brief

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a product brief collaboratively without losing context?

Creating a product brief collaboratively requires a structured workflow with step-file architecture and frontmatter state tracking to capture context. This ensures consistent vision, user, metric, and MVP scope definition without data loss across iterative stages.

What is the best way to define MVP scope and success metrics for a new product?

Defining MVP scope and success metrics is best achieved through guided collaborative discovery. This process enforces sequential execution to systematically capture essential product vision, target users, and measurable goals within a structured document.

Can I resume an incomplete product brief workflow if I pause midway?

You can resume an incomplete product brief workflow seamlessly. The system detects existing workflow state via frontmatter tracking, enabling continuation without data loss by pausing for interactive menu input at each discovery stage.

Do I need markdown files and project configuration to generate a product brief?

Yes, generating a product brief requires access to project configuration and template files. The system reads and writes markdown documents while automatically updating frontmatter state to maintain the structured document throughout the workflow.

How does guided collaborative discovery work for product teams?

Guided collaborative discovery works by presenting interactive menus that pause for user input at each stage. It enforces sequential execution to ensure product teams collaboratively define vision, users, metrics, and MVP scope with final validation.

What happens after completing the product brief generation workflow?

After completing product brief generation, the system provides final validation, status updates, and next-step recommendations. The structured document is generated from a template with automatically updated frontmatter, ready for downstream product development.