bmad-product-brief

Create, update, or validate a product brief. Use when the user wants help producing, editing, or validating a brief.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, highly actionable multi-mode workflow skill with clear sequencing, explicit validation checkpoints, and an appropriate one-level-deep reference to the brief template asset. Its only meaningful weakness is verbosity in the coaching-philosophy prose.

Suggestions

Tighten the Overview and Discovery coaching-philosophy prose, collapsing the repeated pushback/calibration emphasis into a single concise statement to reduce token cost.

Signal the brief-template dependency with a direct reference (e.g. assets/brief-template.md) in addition to the {workflow.brief_template} variable so the asset is visible without config resolution.

Dimension	Reasoning	Score
Conciseness	It is mostly efficient and avoids explaining concepts Claude already knows, but the Overview/Discovery coaching philosophy and repeated emphasis ('not in a hurry', 'make them sweat', 'push back when an answer is thin') could be tightened, fitting the 'mostly efficient but includes some unnecessary explanation or could be tightened' anchor rather than the lean level 3.	2 / 3
Actionability	Concrete executable commands (resolve_customization.py, memlog.py init/append with full flag signatures), explicit path bindings ({doc_workspace}/brief.md), and copy-ready JSON status examples give fully actionable guidance; for an instruction skill this meets the 'concrete, specific guidance' bar.	3 / 3
Workflow Clarity	Activation is a numbered 1-6 sequence, intent modes (Create/Update/Validate) are clearly labeled, and explicit checkpoints appear throughout (confirm every activation step executed before proceeding, halt 'blocked' on ambiguous intent, validate against prior decisions, finalize memlog audit), matching the 'clear sequence with explicit validation steps' anchor.	3 / 3
Progressive Disclosure	The body is organized into clear sections (Activation, Intent Operating Modes, Headless Mode, Discovery, Constraints, Finalize) with the detailed brief template split one level deep into assets/brief-template.md and no nested reference chains, matching the 'clear overview with well-signaled one-level-deep references' anchor.	3 / 3
	Total	11 / 12 Passed

Description

85%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A clear, third-person description that explicitly answers both what and when with a 'Use when...' trigger and three distinct, specific actions. Its only weakness is trigger-term coverage, which omits common natural phrasings like 'write' or 'draft' a brief.

Suggestions

Add common natural phrasings (e.g. 'write', 'draft', or 'review a product brief') alongside 'producing, editing, validating' to broaden trigger-term coverage.

Include 'product brief' in the 'Use when...' clause itself so the trigger surfaces the distinct niche term users are most likely to say.

Dimension	Reasoning	Score
Specificity	"Create, update, or validate a product brief" names the domain and three concrete actions, matching the 'lists multiple specific concrete actions' anchor rather than the level-2 'names domain and some actions, but not comprehensive'.	3 / 3
Completeness	It states what it does ("Create, update, or validate a product brief") and an explicit 'Use when...' trigger for when, clearly answering both what and when; not level 2 because the when clause is explicit, not merely implied.	3 / 3
Trigger Term Quality	"Use when the user wants help producing, editing, or validating a brief" gives some natural keywords but misses common variations users would actually say (write, draft, review a brief), fitting the 'some relevant keywords but missing common variations' anchor and falling short of the level-3 broad coverage.	2 / 3
Distinctiveness Conflict Risk	"product brief" is a clear niche with distinct triggers unlikely to overlap with other skills, matching the 'clear niche with distinct triggers; unlikely to conflict' anchor.	3 / 3
	Total	11 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: bmad-code-org/BMAD-METHOD
Path: src/bmm-skills/1-analysis/bmad-product-brief/SKILL.md
Commit: bb45db4

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.