aj-geddes/bmad-product-brief
bmad-planning-orchestrator/skills/bmad-product-brief/SKILL.md
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 a product brief", "let's do discovery", "help me define my product", "what problem are we solving", "capture our product vision", "update the product brief", "validate the brief", "check if the brief is complete", "run discovery", "start a product brief", "brainstorm the product", or "I want to plan a product". Supports three intents: - Create — guided discovery conversation that fills and writes the brief - Update — amends one or more sections in an existing brief - Validate — completeness check against all required sections Output is a planning artifact only — no code is written or run.
$ install --global
skillsauthnpx skillsauth add aj-geddes/claude-code-bmad-skills bmad-product-briefInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 20, 2026, 4:07 AM110.9s4 files scanned
SKILL.md
- name:
- bmad-product-brief
- description:
- |
- Use when the user says:
- create a product brief", "I need a product brief",
- allowed-tools:
- Read, Write, Edit, Bash, Glob, Grep, TodoWrite
BMAD Product Brief
Phase: Analysis (Phase 1)
Upstream counterpart: bmad-business-analyst
Output artifact: bmad-output/product-brief.md
Intent Detection
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?
- Target Users — Primary and secondary personas. Roles, goals, pain points, technical proficiency.
- Proposed Solution — Core value proposition, key capabilities (MVP scope vs. future). What makes it different?
- Goals & Constraints — Business goals, non-negotiable constraints (regulatory, platform, budget, timeline).
- Success Metrics — SMART metrics with baselines and targets. What does success look like at 3 / 6 / 12 months?
- Market & Competition — Key competitors, gaps, differentiation angle. (Optional: use WebSearch if the user wants research.)
- Risks & Assumptions — Top 3–5 risks with probability, impact, and mitigation. Critical assumptions to validate.
- Dependencies & Next Steps — Internal/external dependencies, blockers, recommended handoff.
Facilitation Rules
- Ask one focused question (with 1–3 probing sub-questions) before moving on.
- If an answer is vague, probe with "Why?" up to 5 times (5 Whys) or "What does that mean for users specifically?"
- After each section, summarize what you heard and ask "Does that capture it correctly?"
- Keep the tone conversational — you are Mary the Analyst, a sharp listener, not a form engine.
- Offer to run
scripts/discovery-checklist.shif the user wants the full structured question list printed.
Writing the Brief
After all sections are confirmed:
- Populate
${CLAUDE_PLUGIN_ROOT}/skills/bmad-product-brief/templates/product-brief.template.mdwith the gathered answers. - Write the result to
bmad-output/product-brief-<slug>-<YYYY-MM-DD>.md(createbmad-output/if absent). - Log the decision to
bmad-output/decision-log.md(append: date, action, brief filename). - Print a summary (problem, users, key capabilities, top metric, next step).
Update Intent
- Read the existing brief (ask for the path if not obvious; search
bmad-output/product-brief*.md). - Ask: "Which section(s) do you want to update?"
- For each section named, show the current content and ask for the replacement or addition.
- Edit the file in place (do not rewrite untouched sections).
- Append a change note at the bottom:
<!-- Updated <DATE>: <section(s) changed> -->. - Log the update to
bmad-output/decision-log.md.
Validate Intent
Run the validation script against the brief file:
bash ${CLAUDE_PLUGIN_ROOT}/skills/bmad-product-brief/scripts/validate-brief.sh <path-to-brief>
Interpret the output and present findings conversationally:
- List any missing sections and offer to fill them interactively.
- List unfilled
{{PLACEHOLDER}}tokens. - Surface quality warnings (no metrics, no dates, etc.).
- If the brief is complete (100% + no placeholders), recommend handoff to the Product Manager.
Output Folder Convention
All artifacts go under the user-configured output folder, defaulting to bmad-output/:
| File | Description |
|------|-------------|
| bmad-output/product-brief-<slug>-<YYYY-MM-DD>.md | The brief itself |
| bmad-output/decision-log.md | Running log of planning decisions |
Handoff Criteria
The brief is ready for handoff to the Product Manager (PRD creation) when:
- All 8 sections are present and filled.
- At least one SMART success metric is defined.
- MVP scope is distinguished from future scope.
- Top risks and assumptions are documented.
validate-brief.shexits 0.
State clearly: "The product brief is complete. Recommend handing off to the Product Manager to create the PRD."
Subagent Strategy
For Create with optional market research, fan out after the discovery conversation:
| Agent | Task | Output |
|-------|------|--------|
| Agent 1 (optional) | Competitive landscape research via WebSearch | bmad-output/competitive-snapshot.md |
| Agent 2 (optional) | User needs / persona synthesis from notes | bmad-output/persona-notes.md |
Main context assembles final brief from subagent outputs plus the conversation notes. Launch subagents only when the user requests research depth beyond what they can supply verbally.
Available Resources
${CLAUDE_PLUGIN_ROOT}/skills/bmad-product-brief/templates/product-brief.template.md— Brief template${CLAUDE_PLUGIN_ROOT}/skills/bmad-product-brief/scripts/validate-brief.sh— Completeness validator${CLAUDE_PLUGIN_ROOT}/skills/bmad-product-brief/scripts/discovery-checklist.sh— Full question list (printable)
Part of the BMAD Planning & Orchestrator plugin — a Claude Code harness for the BMAD Method by the BMAD Code Organization (https://github.com/bmad-code-org/BMAD-METHOD). Implements the spirit of
bmad-business-analyst. All methodology credit belongs to the BMAD Code Organization.
Related Skills
aj-geddes/bmad-ux
testing
VerifiedTrustedCommunity
Solutioning-phase UX planning skill (optional; activate when the project has a UI). Produces TWO planning documents: DESIGN.md (the visual system — design tokens, color palette, typography, spacing, component specs, WCAG 2.1 AA contract) and EXPERIENCE.md (user journeys, flow diagrams, screen states, error/empty/loading handling). Use when the user says "design the UX", "create UX planning docs", "define the design system", "map the user flows", "UX for this feature", "wireframe the flows", "what are the user journeys", "accessibility design", "WCAG compliance", "design tokens", "responsive design plan", "mobile-first design", or "create DESIGN.md / EXPERIENCE.md". Runs after architecture is drafted and before stories are created. Supports Create / Update / Validate intents.
451SKILL.mdUpdated Jun 20, 2026
aj-geddes/bmad-tech-spec
testing
VerifiedTrustedCommunity
Quick Flow lightweight technical specification for small-scope work (1-15 stories). Replaces the full PRD + architecture pair when scope is small and requirements are clear. Produces bmad-output/tech-spec.md as the single planning artifact before story creation. Use when the user says: "write a tech spec", "create a technical specification", "I need a tech spec for this feature", "quick spec", "small project spec", "we don't need a full PRD", "just a tech spec", "spec out this change", "document this feature". QUICK FLOW TRACK ONLY (1-15 stories). If scope grows beyond ~15 stories or involves multiple teams / external integrations at scale, stop and redirect to bmad-prd + bmad-architecture instead — those skills are built for that complexity. Supports three intents: Create (new spec), Update (revise an existing tech-spec.md), Validate (review a draft for completeness against BMAD criteria).
451SKILL.mdUpdated Jun 20, 2026
aj-geddes/bmad-sprint-planning
tools
VerifiedTrustedCommunity
Orchestration handoff bridge: emits and maintains sprint-status.yaml as the project's sequencing system-of-record. Orders stories by epic then dependency, assigns parallel-set (wave) membership, and drives the status lifecycle (backlog → ready-for-dev → in-progress → review → done) as a view — never as a metric. Use when the user says "sequence the stories", "build the sprint status", "plan the waves", "create sprint-status.yaml", "assign parallel sets", "order stories by dependency", "what can run in parallel", "set up story sequencing", "initialize sprint tracking", "ready the backlog", or "prepare for dev handoff". Also triggers on "sprint planning" when the project already has epics defined. SCOPE: SEQUENCING AND ORCHESTRATION ONLY. No velocity, no burndown, no committed points, no coverage metrics. Capacity is expressed as wave width (concurrent story count), not points. The final artifact is a ready-for-dev handoff manifest; implementation is delegated to external dev tools.
451SKILL.mdUpdated Jun 20, 2026
aj-geddes/bmad-spec
development
VerifiedTrustedCommunity
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 problem", "help me scope this", "summarize what we're building", "I have a PRD but need a kernel", "what are we actually solving?", or drops raw text/transcript and asks for structure. Also use when starting any new initiative and a clean shared definition is missing.
451SKILL.mdUpdated Jun 20, 2026