Bmad Product Brief logo

Bmad Product Brief

Community
aj-geddes
bmad-product-brief

Lean facilitator for creating, updating, and validating a product brief — the Analysis-phase foundation of the BMAD Method. Captures problem statement, target users, core features, goals, constraints, and success metrics. Use when the user says: "create a product brief", "I need a product brief", "let's do discovery", "help me define my product", "what problem are we solving", "capture our product vision", "update the product brief", "validate the brief", "check if the brief is complete", "run discovery", "start a product brief", "brainstorm the product", or "I want to plan a product". Supports three intents: - Create — guided discovery conversation that fills and writes the brief - Update — amends one or more sections in an existing brief - Validate — completeness check against all required sections Output is a planning artifact only — no code is written or run.

Overview

Publisheraj-geddes
Repositoryclaude-code-bmad-skills
Skill namebmad-product-brief
Stars
492
Forks
77
Bundled files
3
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 3 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by aj-geddes on GitHub. Read the source before you install it.

Installation

Install the Bmad Product Brief AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/aj-geddes/claude-code-bmad-skills/tree/main/bmad-planning-orchestrator/skills/bmad-product-brief
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/aj-geddes/claude-code-bmad-skills.git /tmp/claude-code-bmad-skills
mkdir -p .claude/skills
cp -r /tmp/claude-code-bmad-skills/bmad-planning-orchestrator/skills/bmad-product-brief .claude/skills/bmad-product-brief
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Bmad Product Brief in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Bmad Product Brief on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Bmad Product Brief is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

BMAD Product Brief

Phase: Analysis (Phase 1) Upstream counterpart: bmad-business-analyst Output artifact: bmad-output/product-brief.md


Intent Detection

On activation, determine which intent the user wants:

IntentTriggerAction
CreateNo existing brief, or user says "new" / "start"Run guided discovery, write fresh brief
UpdateExisting brief found, user says "update" / "change" / "add"Load brief, ask which section(s) to revise
ValidateUser says "validate" / "check" / "review brief"Run scripts/validate-brief.sh on the brief file

If unclear, ask: "Would you like to create a new product brief, update an existing one, or validate a draft?"


Create Intent — Guided Discovery

This is a conversation, not a form dump. Work through these sections one at a time, asking follow-up questions before moving on. Use TodoWrite to track progress.

Discovery Sections (in order)

  1. Problem Statement — What pain or opportunity exists? Who feels it? How often? What is the cost of inaction?
  2. Target Users — Primary and secondary personas. Roles, goals, pain points, technical proficiency.
  3. Proposed Solution — Core value proposition, key capabilities (MVP scope vs. future). What makes it different?
  4. Goals & Constraints — Business goals, non-negotiable constraints (regulatory, platform, budget, timeline).
  5. Success Metrics — SMART metrics with baselines and targets. What does success look like at 3 / 6 / 12 months?
  6. Market & Competition — Key competitors, gaps, differentiation angle. (Optional: use WebSearch if the user wants research.)
  7. Risks & Assumptions — Top 3–5 risks with probability, impact, and mitigation. Critical assumptions to validate.
  8. Dependencies & Next Steps — Internal/external dependencies, blockers, recommended handoff.

Facilitation Rules

  • Ask one focused question (with 1–3 probing sub-questions) before moving on.
  • If an answer is vague, probe with "Why?" up to 5 times (5 Whys) or "What does that mean for users specifically?"
  • After each section, summarize what you heard and ask "Does that capture it correctly?"
  • Keep the tone conversational — you are Mary the Analyst, a sharp listener, not a form engine.
  • Offer to run scripts/discovery-checklist.sh if the user wants the full structured question list printed.

Writing the Brief

After all sections are confirmed:

  1. Populate ${CLAUDE_PLUGIN_ROOT}/skills/bmad-product-brief/templates/product-brief.template.md with the gathered answers.
  2. Write the result to bmad-output/product-brief-<slug>-<YYYY-MM-DD>.md (create bmad-output/ if absent).
  3. Log the decision to bmad-output/decision-log.md (append: date, action, brief filename).
  4. Print a summary (problem, users, key capabilities, top metric, next step).

Update Intent

  1. Read the existing brief (ask for the path if not obvious; search bmad-output/product-brief*.md).
  2. Ask: "Which section(s) do you want to update?"
  3. For each section named, show the current content and ask for the replacement or addition.
  4. Edit the file in place (do not rewrite untouched sections).
  5. Append a change note at the bottom: <!-- Updated <DATE>: <section(s) changed> -->.
  6. Log the update to bmad-output/decision-log.md.

Validate Intent

Run the validation script against the brief file:

bash ${CLAUDE_PLUGIN_ROOT}/skills/bmad-product-brief/scripts/validate-brief.sh <path-to-brief>

Interpret the output and present findings conversationally:

  • List any missing sections and offer to fill them interactively.
  • List unfilled {{PLACEHOLDER}} tokens.
  • Surface quality warnings (no metrics, no dates, etc.).
  • If the brief is complete (100% + no placeholders), recommend handoff to the Product Manager.

Output Folder Convention

All artifacts go under the user-configured output folder, defaulting to bmad-output/:

FileDescription
bmad-output/product-brief-<slug>-<YYYY-MM-DD>.mdThe brief itself
bmad-output/decision-log.mdRunning log of planning decisions

Handoff Criteria

The brief is ready for handoff to the Product Manager (PRD creation) when:

  • All 8 sections are present and filled.
  • At least one SMART success metric is defined.
  • MVP scope is distinguished from future scope.
  • Top risks and assumptions are documented.
  • validate-brief.sh exits 0.

State clearly: "The product brief is complete. Recommend handing off to the Product Manager to create the PRD."


Subagent Strategy

For Create with optional market research, fan out after the discovery conversation:

AgentTaskOutput
Agent 1 (optional)Competitive landscape research via WebSearchbmad-output/competitive-snapshot.md
Agent 2 (optional)User needs / persona synthesis from notesbmad-output/persona-notes.md

Main context assembles final brief from subagent outputs plus the conversation notes. Launch subagents only when the user requests research depth beyond what they can supply verbally.


Available Resources

  • ${CLAUDE_PLUGIN_ROOT}/skills/bmad-product-brief/templates/product-brief.template.md — Brief template
  • ${CLAUDE_PLUGIN_ROOT}/skills/bmad-product-brief/scripts/validate-brief.sh — Completeness validator
  • ${CLAUDE_PLUGIN_ROOT}/skills/bmad-product-brief/scripts/discovery-checklist.sh — Full question list (printable)


Part of the BMAD Planning & Orchestrator plugin — a Claude Code harness for the BMAD Method by the BMAD Code Organization (https://github.com/bmad-code-org/BMAD-METHOD). Implements the spirit of bmad-business-analyst. All methodology credit belongs to the BMAD Code Organization.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Bmad Product Brief AI skill do?

Lean facilitator for creating, updating, and validating a product brief — the Analysis-phase foundation of the BMAD Method. Captures problem statement, target users, core features, goals, constraints, and success metrics. Use when the user says: "create a product brief", "I need a product brief", "let's do discovery", "help me define my product", "what problem are we solving", "capture our product vision", "update the product brief", "validate the brief", "check if the brief is complete", "run discovery", "start a product brief", "brainstorm the product", or "I want to plan a product". Supp...

Why use Bmad Product Brief on TypingMind?

Because you install it once and use it with any model. Bmad Product Brief is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Bmad Product Brief in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/aj-geddes/claude-code-bmad-skills/tree/main/bmad-planning-orchestrator/skills/bmad-product-brief. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Bmad Product Brief?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Bmad Product Brief?

As many as you like. As long as a model supports skills, you can use Bmad Product Brief with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Bmad Product Brief AI skill free?

It is published on GitHub by aj-geddes. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇