bmad-product-brief

Name: bmad-product-brief
Author: aj-geddes

26installs73forks

How to install bmad-product-brief?

aj-geddes/claude-code-bmad-skills/bmad-product-brief

$npx -y skills add aj-geddes/claude-code-bmad-skills --skill bmad-product-brief

Installs into the current project.

Summary

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

Files · 1

View on GitHub

SKILL.md

1	# BMAD Product Brief
2
3	Phase: Analysis (Phase 1)
4	Upstream counterpart: `bmad-business-analyst`
5	Output artifact: `bmad-output/product-brief.md`
6
7	---
8
9	## Intent Detection
10
11	On activation, determine which intent the user wants:
12
13	\| Intent \| Trigger \| Action \|
14	\|--------\|---------\|--------\|
15	\| Create \| No existing brief, or user says "new" / "start" \| Run guided discovery, write fresh brief \|
16	\| Update \| Existing brief found, user says "update" / "change" / "add" \| Load brief, ask which section(s) to revise \|
17	\| Validate \| User says "validate" / "check" / "review brief" \| Run `scripts/validate-brief.sh` on the brief file \|
18
19	If unclear, ask: "Would you like to create a new product brief, update an existing one, or validate a draft?"
20
21	---
22
23	## Create Intent — Guided Discovery
24
25	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.
26
27	### Discovery Sections (in order)
28
29	1. Problem Statement — What pain or opportunity exists? Who feels it? How often? What is the cost of inaction?
30	2. Target Users — Primary and secondary personas. Roles, goals, pain points, technical proficiency.
31	3. Proposed Solution — Core value proposition, key capabilities (MVP scope vs. future). What makes it different?
32	4. Goals & Constraints — Business goals, non-negotiable constraints (regulatory, platform, budget, timeline).
33	5. Success Metrics — SMART metrics with baselines and targets. What does success look like at 3 / 6 / 12 months?
34	6. Market & Competition — Key competitors, gaps, differentiation angle. (Optional: use WebSearch if the user wants research.)
35	7. Risks & Assumptions — Top 3–5 risks with probability, impact, and mitigation. Critical assumptions to validate.
36	8. Dependencies & Next Steps — Internal/external dependencies, blockers, recommended handoff.
37
38	### Facilitation Rules
39
40	- Ask one focused question (with 1–3 probing sub-questions) before moving on.
41	- If an answer is vague, probe with "Why?" up to 5 times (5 Whys) or "What does that mean for users specifically?"
42	- After each section, summarize what you heard and ask "Does that capture it correctly?"
43	- Keep the tone conversational — you are Mary the Analyst, a sharp listener, not a form engine.
44	- Offer to run `scripts/discovery-checklist.sh` if the user wants the full structured question list printed.
45
46	### Writing the Brief
47
48	After all sections are confirmed:
49	1. Populate `${CLAUDE_PLUGIN_ROOT}/skills/bmad-product-brief/templates/product-brief.template.md` with the gathered answers.
50	2. Write the result to `bmad-output/product-brief-<slug>-<YYYY-MM-DD>.md` (create `bmad-output/` if absent).
51	3. Log the decision to `bmad-output/decision-log.md` (append: date, action, brief filename).
52	4. Print a summary (problem, users, key capabilities, top metric, next step).
53
54	---
55
56	## Update Intent
57
58	1. Read the existing brief (ask for the path if not obvious; search `bmad-output/product-brief*.md`).
59	2. Ask: "Which section(s) do you want to update?"
60	3. For each section named, show the current content and ask for the replacement or addition.
61	4. Edit the file in place (do not rewrite untouched sections).
62	5. Append a change note at the bottom: `<!-- Updated <DATE>: <section(s) changed> -->`.
63	6. Log the update to `bmad-output/decision-log.md`.
64
65	---
66
67	## Validate Intent
68
69	Run the validation script against the brief file:
70
71	```
72	bash ${CLAUDE_PLUGIN_ROOT}/skills/bmad-product-brief/scripts/validate-brief.sh <path-to-brief>
73	```
74
75	Interpret the output and present findings conversationally:
76	- List any missing sections and offer to fill them interactively.
77	- List unfilled `{{PLACEHOLDER}}` tokens.
78	- Surface quality warnings (no metrics, no dates, etc.).
79	- If the brief is complete (100% + no placeholders), recommend handoff to the Product Manager.
80
81	---
82
83	## Output Folder Convention
84
85	All artifacts go under the user-configured output folder, defaulting to

People who liked this also viewed

6 picks

Type

bmad-product-brief

26installs73forks

View on GitHub

How to install bmad-product-brief?

aj-geddes/claude-code-bmad-skills/bmad-product-brief

$npx -y skills add aj-geddes/claude-code-bmad-skills --skill bmad-product-brief

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# BMAD Product Brief
2
3	Phase: Analysis (Phase 1)
4	Upstream counterpart: `bmad-business-analyst`
5	Output artifact: `bmad-output/product-brief.md`
6
7	---
8
9	## Intent Detection
10
11	On activation, determine which intent the user wants:
12
13	\| Intent \| Trigger \| Action \|
14	\|--------\|---------\|--------\|
15	\| Create \| No existing brief, or user says "new" / "start" \| Run guided discovery, write fresh brief \|
16	\| Update \| Existing brief found, user says "update" / "change" / "add" \| Load brief, ask which section(s) to revise \|
17	\| Validate \| User says "validate" / "check" / "review brief" \| Run `scripts/validate-brief.sh` on the brief file \|
18
19	If unclear, ask: "Would you like to create a new product brief, update an existing one, or validate a draft?"
20
21	---
22
23	## Create Intent — Guided Discovery
24
25	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.
26
27	### Discovery Sections (in order)
28
29	1. Problem Statement — What pain or opportunity exists? Who feels it? How often? What is the cost of inaction?
30	2. Target Users — Primary and secondary personas. Roles, goals, pain points, technical proficiency.
31	3. Proposed Solution — Core value proposition, key capabilities (MVP scope vs. future). What makes it different?
32	4. Goals & Constraints — Business goals, non-negotiable constraints (regulatory, platform, budget, timeline).
33	5. Success Metrics — SMART metrics with baselines and targets. What does success look like at 3 / 6 / 12 months?
34	6. Market & Competition — Key competitors, gaps, differentiation angle. (Optional: use WebSearch if the user wants research.)
35	7. Risks & Assumptions — Top 3–5 risks with probability, impact, and mitigation. Critical assumptions to validate.
36	8. Dependencies & Next Steps — Internal/external dependencies, blockers, recommended handoff.
37
38	### Facilitation Rules
39
40	- Ask one focused question (with 1–3 probing sub-questions) before moving on.
41	- If an answer is vague, probe with "Why?" up to 5 times (5 Whys) or "What does that mean for users specifically?"
42	- After each section, summarize what you heard and ask "Does that capture it correctly?"
43	- Keep the tone conversational — you are Mary the Analyst, a sharp listener, not a form engine.
44	- Offer to run `scripts/discovery-checklist.sh` if the user wants the full structured question list printed.
45
46	### Writing the Brief
47
48	After all sections are confirmed:
49	1. Populate `${CLAUDE_PLUGIN_ROOT}/skills/bmad-product-brief/templates/product-brief.template.md` with the gathered answers.
50	2. Write the result to `bmad-output/product-brief-<slug>-<YYYY-MM-DD>.md` (create `bmad-output/` if absent).
51	3. Log the decision to `bmad-output/decision-log.md` (append: date, action, brief filename).
52	4. Print a summary (problem, users, key capabilities, top metric, next step).
53
54	---
55
56	## Update Intent
57
58	1. Read the existing brief (ask for the path if not obvious; search `bmad-output/product-brief*.md`).
59	2. Ask: "Which section(s) do you want to update?"
60	3. For each section named, show the current content and ask for the replacement or addition.
61	4. Edit the file in place (do not rewrite untouched sections).
62	5. Append a change note at the bottom: `<!-- Updated <DATE>: <section(s) changed> -->`.
63	6. Log the update to `bmad-output/decision-log.md`.
64
65	---
66
67	## Validate Intent
68
69	Run the validation script against the brief file:
70
71	```
72	bash ${CLAUDE_PLUGIN_ROOT}/skills/bmad-product-brief/scripts/validate-brief.sh <path-to-brief>
73	```
74
75	Interpret the output and present findings conversationally:
76	- List any missing sections and offer to fill them interactively.
77	- List unfilled `{{PLACEHOLDER}}` tokens.
78	- Surface quality warnings (no metrics, no dates, etc.).
79	- If the brief is complete (100% + no placeholders), recommend handoff to the Product Manager.
80
81	---
82
83	## Output Folder Convention
84
85	All artifacts go under the user-configured output folder, defaulting to

People who liked this also viewed

6 picks

Type