bmad-prfaq

Name: bmad-prfaq
Author: aj-geddes

467stars73forks

How to install bmad-prfaq?

aj-geddes/claude-code-bmad-skills/bmad-prfaq

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

Installs into the current project.

Summary

Amazon-style Working-Backwards PRFAQ: a future press release plus internal and external FAQs that stress-test a product concept before any building begins. Produces prfaq.md in the configured output folder. Use when the user says: "write a PRFAQ", "working backwards", "press rele

Files · 1

View on GitHub

SKILL.md

1	# BMAD PRFAQ
2
3	Role: Pre-Phase Analysis — Working-Backwards stress-test
4
5	Function: Guide the user through the Amazon Working-Backwards method to
6	produce a PRFAQ document (`prfaq.md`) that crystallises the product vision,
7	validates the concept, and surfaces hard questions before a PRD, architecture,
8	or a single line of code is written.
9
10	## When to Use This Skill
11
12	Use when you need to:
13	- Validate a product concept before committing to a PRD or sprint plan
14	- Write a future press release that forces clarity on customer value
15	- Stress-test assumptions with a structured internal FAQ
16	- Prepare customer-facing answers before launch
17	- Update or validate an existing PRFAQ document
18	- Choose a BMAD planning track (the PRFAQ often precedes or replaces the
19	product brief for Working-Backwards teams)
20
21	## The Working-Backwards Method
22
23	Working-Backwards starts from the desired customer outcome and reasons
24	backward to the product. The PRFAQ has two parts:
25
26	\| Part \| Purpose \|
27	\|------\|---------\|
28	\| Press Release \| Articulate the customer value as if the product already shipped \|
29	\| Internal FAQ \| Surface hard business and technical questions the team must answer \|
30	\| External FAQ \| Anticipate questions a curious customer or press contact would ask \|
31
32	The process forces concrete answers to the hardest questions now, not after
33	months of building.
34
35	## Three Intents
36
37	This skill supports three modes. Identify intent from context:
38
39	\| Intent \| Trigger \| Output \|
40	\|--------\|---------\|--------\|
41	\| Create \| No existing PRFAQ; new concept \| Full `prfaq.md` from scratch \|
42	\| Update \| Existing PRFAQ; requirements changed \| Revised `prfaq.md` with decision log entry \|
43	\| Validate \| Draft PRFAQ exists; needs critique \| Critique report; annotated checklist \|
44
45	## Core Workflow
46
47	### 1. Orient (all intents)
48
49	- Check output folder for existing `prfaq.md`, `project-context.md`, and
50	`decision-log.md`.
51	- Confirm intent with the user (Create / Update / Validate).
52	- For Create: proceed to Step 2.
53	- For Update: read existing doc, identify changed sections, proceed to Step 4.
54	- For Validate: read existing doc, run the Validation Checklist (see below),
55	produce a critique; stop — do not rewrite unless the user asks.
56
57	### 2. Gather (Create / Update)
58
59	Ask the minimum questions needed to fill the template. Stop after each cluster
60	and confirm before moving on. Suggested clusters:
61
62	Cluster A — Customer & Problem
63	- Who is the target customer (role, segment, context)?
64	- What is the specific problem or unmet need?
65	- How do they currently cope without this product?
66
67	Cluster B — Product & Value
68	- What does the product do in one sentence?
69	- What is the single most important customer benefit?
70	- What measurable outcome does the customer achieve?
71
72	Cluster C — Differentiation & Availability
73	- How is this different from existing solutions?
74	- When and how will customers get it?
75	- What is the call to action at launch?
76
77	Cluster D — Hard Questions (Internal)
78	- What are the top 3 risks or unknowns?
79	- What must be true technically for this to work?
80	- What does success look like in 6 months? 12 months?
81
82	Cluster E — Customer Questions (External)
83	- What will customers ask first?
84	- What might make them hesitate?
85	- What evidence or proof do they need?
86
87	### 3. Draft Press Release
88
89	Use the template at `${CLAUDE_PLUGIN_ROOT}/skills/bmad-prfaq/templates/prfaq.template.md`.
90
91	Fill in order:
92	1. Headline — product name + primary customer benefit in one line
93	2. Subheadline — who it is for and the key outcome
94	3. Opening paragraph — problem context (2-3 sentences)
95	4. Problem paragraph — paint the pain without naming the solution
96	5. Solution paragraph — introduce the product and its core capability
97	6. Benefit paragraphs — 2-3 paragraphs, one key benefit each
98	7. Customer quote — a realistic quote from a named persona
99	8. Call to action — how to get it, when, what to do next
100	9. Company quote — internal leader framing strategic intent
101
102	Keep the press release under 600 words. If you cannot keep it short, the
103	concept is not clear enough — ask more questions.
104
105	### 4. Draft Internal FAQ
106
107	10-15 questions that the leadership team, investors, or a skeptical engineer
108	would ask. R

People who liked this also viewed

6 picks

Type

bmad-prfaq

467stars73forks

View on GitHub

How to install bmad-prfaq?

aj-geddes/claude-code-bmad-skills/bmad-prfaq

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

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# BMAD PRFAQ
2
3	Role: Pre-Phase Analysis — Working-Backwards stress-test
4
5	Function: Guide the user through the Amazon Working-Backwards method to
6	produce a PRFAQ document (`prfaq.md`) that crystallises the product vision,
7	validates the concept, and surfaces hard questions before a PRD, architecture,
8	or a single line of code is written.
9
10	## When to Use This Skill
11
12	Use when you need to:
13	- Validate a product concept before committing to a PRD or sprint plan
14	- Write a future press release that forces clarity on customer value
15	- Stress-test assumptions with a structured internal FAQ
16	- Prepare customer-facing answers before launch
17	- Update or validate an existing PRFAQ document
18	- Choose a BMAD planning track (the PRFAQ often precedes or replaces the
19	product brief for Working-Backwards teams)
20
21	## The Working-Backwards Method
22
23	Working-Backwards starts from the desired customer outcome and reasons
24	backward to the product. The PRFAQ has two parts:
25
26	\| Part \| Purpose \|
27	\|------\|---------\|
28	\| Press Release \| Articulate the customer value as if the product already shipped \|
29	\| Internal FAQ \| Surface hard business and technical questions the team must answer \|
30	\| External FAQ \| Anticipate questions a curious customer or press contact would ask \|
31
32	The process forces concrete answers to the hardest questions now, not after
33	months of building.
34
35	## Three Intents
36
37	This skill supports three modes. Identify intent from context:
38
39	\| Intent \| Trigger \| Output \|
40	\|--------\|---------\|--------\|
41	\| Create \| No existing PRFAQ; new concept \| Full `prfaq.md` from scratch \|
42	\| Update \| Existing PRFAQ; requirements changed \| Revised `prfaq.md` with decision log entry \|
43	\| Validate \| Draft PRFAQ exists; needs critique \| Critique report; annotated checklist \|
44
45	## Core Workflow
46
47	### 1. Orient (all intents)
48
49	- Check output folder for existing `prfaq.md`, `project-context.md`, and
50	`decision-log.md`.
51	- Confirm intent with the user (Create / Update / Validate).
52	- For Create: proceed to Step 2.
53	- For Update: read existing doc, identify changed sections, proceed to Step 4.
54	- For Validate: read existing doc, run the Validation Checklist (see below),
55	produce a critique; stop — do not rewrite unless the user asks.
56
57	### 2. Gather (Create / Update)
58
59	Ask the minimum questions needed to fill the template. Stop after each cluster
60	and confirm before moving on. Suggested clusters:
61
62	Cluster A — Customer & Problem
63	- Who is the target customer (role, segment, context)?
64	- What is the specific problem or unmet need?
65	- How do they currently cope without this product?
66
67	Cluster B — Product & Value
68	- What does the product do in one sentence?
69	- What is the single most important customer benefit?
70	- What measurable outcome does the customer achieve?
71
72	Cluster C — Differentiation & Availability
73	- How is this different from existing solutions?
74	- When and how will customers get it?
75	- What is the call to action at launch?
76
77	Cluster D — Hard Questions (Internal)
78	- What are the top 3 risks or unknowns?
79	- What must be true technically for this to work?
80	- What does success look like in 6 months? 12 months?
81
82	Cluster E — Customer Questions (External)
83	- What will customers ask first?
84	- What might make them hesitate?
85	- What evidence or proof do they need?
86
87	### 3. Draft Press Release
88
89	Use the template at `${CLAUDE_PLUGIN_ROOT}/skills/bmad-prfaq/templates/prfaq.template.md`.
90
91	Fill in order:
92	1. Headline — product name + primary customer benefit in one line
93	2. Subheadline — who it is for and the key outcome
94	3. Opening paragraph — problem context (2-3 sentences)
95	4. Problem paragraph — paint the pain without naming the solution
96	5. Solution paragraph — introduce the product and its core capability
97	6. Benefit paragraphs — 2-3 paragraphs, one key benefit each
98	7. Customer quote — a realistic quote from a named persona
99	8. Call to action — how to get it, when, what to do next
100	9. Company quote — internal leader framing strategic intent
101
102	Keep the press release under 600 words. If you cannot keep it short, the
103	concept is not clear enough — ask more questions.
104
105	### 4. Draft Internal FAQ
106
107	10-15 questions that the leadership team, investors, or a skeptical engineer
108	would ask. R

People who liked this also viewed

6 picks

Type