Agent skill · product strategy · aj-geddes
bmad-product-brief
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.
Why this skill is useful
Adds a structured approach to product brief creation and validation, including specific scripts for validation and checklist management.
What it needs
Requires todowrite installed locally. About 4k tokens when loaded. Last updated 2026-06-20. 471 stars on the source repository.
What this skill does
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) 1. Problem Statement — What pain or opportunity exists? Who feels it? How often? What is the cost of inaction? 2. Target Users — Primary and secondary personas. Roles, goals, pain points, technical proficiency. 3. Proposed Solution — Core value proposition, key capabilities (MVP scope vs. future). What makes it different? 4. Goals & Constraints — Business goals, non-negotiable constraints (regulatory, platform, budget, timeline). 5. Success Metrics — SMART metrics with baselines and targets. What does success look like at 3 / 6 / 12 months? 6. Market & Competition — Key competitors, gaps, differentiation angle. (Optional: use WebSearch if the user wants research.) 7. Risks & Assumptions — Top 3–5 risks with probability, impact, and mitigation. Critical assumptions to validate. 8. Dependencies & Next Steps — Internal/external dependencies, blockers, recommended handoff. Facilitation Rules Ask one focused question (with 1–3 probing sub-questions) before moving on. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aj-geddes/bmad-product-brief