bmad-create-product-brief

Guide teams through an interactive workflow to create structured product briefs and save them to a tracker document.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/florian-trehaut/bmad-global --skill bmad-create-product-brief-florian-trehaut
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-create-product-brief
Source: https://github.com/florian-trehaut/bmad-global/tree/main/src/bmm-skills/2-plan-workflows/bmad-create-product-brief
Command: npx skills add https://github.com/florian-trehaut/bmad-global --skill bmad-create-product-brief-florian-trehaut

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create product briefs through an interactive guided workflow that captures vision, users, metrics, scope, and risks, then saves the result to a tracker document.

Core Features & Use Cases

  • Interactive elicitation steps for Vision, Users, Metrics, Scope, Risks, and Summary.
  • Saves the completed brief to the tracker under the appropriate project or Meta project.
  • Scales to multiple briefs and supports exporting to PRDs.

Quick Start

Start the interactive brief workflow to begin collecting your vision, users, metrics, and scope.

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 structured product brief for a new feature initiative?

A structured product brief is created through an interactive guided workflow that captures vision, users, metrics, scope, and risks, then saves the result directly to a tracker document. This prevents early assumptions during product discovery by prompting for explicit input.

What is the best way to prepare a product brief for PRD conversion?

Preparing a product brief for PRD conversion involves an interactive elicitation workflow that systematically covers vision, users, metrics, scope, and risks. It scales to multiple briefs and supports exporting to PRDs once the summary is complete.

Can I use an interactive workflow to avoid assumptions during product discovery?

An interactive workflow prevents assumptions during product discovery by enforcing guardrails that prompt for explicit input. It guides cross-functional teams step-by-step through users, metrics, and scope before saving to a tracker.

How does a guided product brief workflow integrate with a tracker document?

A guided product brief workflow integrates with a tracker document by saving the completed brief under the appropriate project or Meta project context. This ensures the brief aligns with existing project tracking after the interactive elicitation steps.

When do I need a tracker-based artifact for product planning?

Tracker-based artifacts for product planning are needed when starting a new feature or product initiative that requires cross-functional team alignment. The interactive workflow ensures the brief captures necessary risks and metrics before saving.