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.
SkillScore50Maintained
Automatic
◆Product Management pack
Last verified 8/19/2026
What it changes
Passed 10 of 20 test cases with the skill, and 5 of 20 without it.
Without skill23%
With skill50%
Checks it passed that the model alone missed
Delegates competitive research to a subagent.
Specifies storing output inside the bmad-output/ directory.
Formats the filename as product-brief-<slug>-<YYYY-MM-DD>.md.
and 5 more in the full report
6 fixed5 passed either way11 still failing0 broke
Pass-rate lift
+27 pp
Tokens
+31%
Agent turns
0%
Response time
-53%
Model gemini-3.6-flashMeasured 8/19/2026v111 of 22 cases passed with skill · 20 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 6
Prompt
What exact bash command should be run to check if bmad-output/product-brief-crm-2025-02-01.md is complete and free of errors?
On activation, determine which intent the user wants:
Intent
Trigger
Action
Create
No existing brief, or user says "new" / "start"
Run guided discovery, write fresh brief
Update
Existing brief found, user says "update" / "change" / "add"
Load brief, ask which section(s) to revise
Validate
User 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)
Problem Statement — What pain or opportunity exists? Who feels it? How often? What is the cost of inaction?
Distills ANY messy input — brain dump, transcript, long PRD, stakeholder notes,
feature request, voice memo — into a tight five-field SPEC.md kernel that any
downstream planning skill can consume. The five fields are: Problem, Capabilities,
Constraints, Non-Goals, Success Metrics.
Use when the user says "create a spec", "write a spec for", "distill this into a
spec", "I have a brain dump", "turn this into something structured", "clean up these
notes", "make a SPEC from", "I want to define the p