bmad-create-product-brief

Guides teams through a step-based workflow to collaboratively create structured product briefs from problem definition to MVP scope.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creates a structured, repeatable process for collaborative product brief creation, ensuring all stakeholders align on the problem, opportunity, and plan before development.

Core Features & Use Cases

  • Step-based workflow that guides discovery from problem definition to MVP scope.
  • Frontmatter-driven state management (stepsCompleted, lastStep, inputDocuments) to support safe continuation.
  • Auto-progression through explicit menu choices while safeguarding against skipping steps.
  • Context loading and tracking of input documents to maintain a single source of truth for the brief.
  • Collaborative, audit-friendly artifact generation suitable for reviews and governance.

Quick Start

Initialize the workflow by confirming the initial input documents and starting Step 1 discovery.

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 collaboratively with stakeholders?

Creating a structured product brief collaboratively requires a step-by-step workflow that guides teams from problem definition to MVP scope, capturing artifacts to ensure stakeholder alignment before development.

What is the best way to align stakeholders on product discovery before development?

Aligning stakeholders on product discovery requires a structured, audit-friendly brief that captures input documents and guides teams through a repeatable workflow from problem definition to MVP scope.

Can I resume a product brief workflow if a collaborative session is interrupted?

You can resume a product brief workflow safely because the system tracks frontmatter state using stepsCompleted, lastStep, and inputDocuments, allowing continuation from the exact point of interruption.

How do I manage input documents during product briefing sessions?

Managing input documents during product briefing sessions involves context loading and tracking within the workflow, maintaining a single source of truth for the brief throughout the discovery process.

Does this product brief workflow prevent teams from skipping discovery steps?

The product brief workflow safeguards against skipping steps by using auto-progression through explicit menu choices, ensuring teams complete discovery sequentially from problem definition to MVP scope.

Is a structured product brief suitable for startup governance and planning?

A structured product brief is suitable for startup governance and planning because it generates audit-friendly artifacts that provide clear alignment on problems and opportunities before development begins.