Skills › BMAD Method › bmod-method › analysis-skills.md
analysis-skills.md
16 lines · skills/bmod-method/help/analysis-skills.md at bd70c64
Most marks come from matching words in the file, so treat them as pointers.
1# Analysis skills in detail
3Read this when the question is about `bmad-product-brief` or `bmad-prfaq`: what each gives, when to pick it, when not to, and how the two relate. Both exist to give Sofia (`bmad-agent-po`) better input for a ticket's requirements.
5**`bmad-product-brief`** — describes a product the user already believes in. The light way to give Sofia good input: more than a hand-written intent file, much less than a full PRD.
6- Gives: a 1-2 page brief (problem, solution, who it serves, what is different, success criteria, scope, vision) that is the user's own, plus an addendum holding detail meant for later documents.
7- Pick when: the user knows what they want and needs it written down, would otherwise hand-write an intent file and wants it sharper, does not need the rigor of a PRD, needs a pitch or alignment document, has material to distill, is short on time (its fast path drafts everything with `[ASSUMPTION]` tags), or has a brief to update or pressure-test.
8- Not when: the user doubts the idea itself → `bmad-prfaq`. The brief never asks whether the product should exist. Requirements need ids, journeys, and metrics, or compliance and many stakeholders are involved → `bmad-prd`.
9- Writes: `{output_folder}/{active_initiative}/brief-<slug>/brief-<slug>.md`.
11**`bmad-prfaq`** — tests whether a concept survives scrutiny, using Amazon's Working Backwards.
12- Gives: a press release for the finished product, hard customer and internal FAQs, and a verdict on what is solid, what needs work, and what could sink it. "Go deeper first" is a good outcome. All market claims are researched.
13- Pick when: the user is unsure the idea is worth building, leads with a technology or a solution instead of a customer problem, is about to commit real money or people, or asks to be challenged.
14- Not when: they cannot name a customer or problem after a few exchanges → `bmad-forge-idea` or `bmad-brainstorming`. They only need a write-up → `bmad-product-brief`.
15- With the brief: most projects need one of the two. Pick by what the user lacks, a clear description or confidence in the idea. A brief after a PRFAQ is reasonable when stakeholders need a short read.
16- Writes: `{output_folder}/{active_initiative}/prfaq-<slug>/prfaq-<slug>.md`, plus `-distillate.md` beside it when finished.
Analysis skills in detail
Read this when the question is about bmad-product-brief or bmad-prfaq: what each gives, when to pick it, when not to, and how the two relate. Both exist to give Sofia (bmad-agent-po) better input for a ticket's requirements.
**bmad-product-brief** — describes a product the user already believes in. The light way to give Sofia good input: more than a hand-written intent file, much less than a full PRD.
- Gives: a 1-2 page brief (problem, solution, who it serves, what is different, success criteria, scope, vision) that is the user's own, plus an addendum holding detail meant for later documents.
- Pick when: the user knows what they want and needs it written down, would otherwise hand-write an intent file and wants it sharper, does not need the rigor of a PRD, needs a pitch or alignment document, has material to distill, is short on time (its fast path drafts everything with
[ASSUMPTION]tags), or has a brief to update or pressure-test. - Not when: the user doubts the idea itself →
bmad-prfaq. The brief never asks whether the product should exist. Requirements need ids, journeys, and metrics, or compliance and many stakeholders are involved →bmad-prd. - Writes:
{output_folder}/{active_initiative}/brief-<slug>/brief-<slug>.md.
**bmad-prfaq** — tests whether a concept survives scrutiny, using Amazon's Working Backwards.
- Gives: a press release for the finished product, hard customer and internal FAQs, and a verdict on what is solid, what needs work, and what could sink it. "Go deeper first" is a good outcome. All market claims are researched.
- Pick when: the user is unsure the idea is worth building, leads with a technology or a solution instead of a customer problem, is about to commit real money or people, or asks to be challenged.
- Not when: they cannot name a customer or problem after a few exchanges →
bmad-forge-ideaorbmad-brainstorming. They only need a write-up →bmad-product-brief. - With the brief: most projects need one of the two. Pick by what the user lacks, a clear description or confidence in the idea. A brief after a PRFAQ is reasonable when stakeholders need a short read.
- Writes:
{output_folder}/{active_initiative}/prfaq-<slug>/prfaq-<slug>.md, plus-distillate.mdbeside it when finished.