bmad-prd

Create, update, and validate product requirements documents through a facilitated discovery workflow.

Updated May 22, 2026
One-click install
npx skills add https://github.com/Asygnuz-S-A-S/one-star --skill bmad-prd-asygnuz-s-a-s
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-prd
Source: https://github.com/Asygnuz-S-A-S/one-star/tree/main/.claude/skills/bmad-prd
Command: npx skills add https://github.com/Asygnuz-S-A-S/one-star --skill bmad-prd-asygnuz-s-a-s

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve? Writing a high-quality PRD requires structured discovery, honest scoping, and rigorous review. This Skill guides users through creating, updating, or validating a PRD with calibrated rigor, decision logging, and multi-reviewer quality gates. ## Core Features & Use Cases - Three intent modes: Create a new PRD from a brain dump, Update an existing PRD against a change signal, or Validate a PRD with a seven-dimension quality rubric without modifying it. - Structured discovery and templates: Elicitation-based discovery, stakes calibration, user journey capture, an Essential Spine template, and an Adapt-In Menu for domain-specific sections like compliance or API contracts. - Reviewer gate and reporting: Parallel reviewer subagents produce findings that are synthesized into HTML and Markdown validation reports, with a decision log and addendum tracking every choice. - Use Case: A product manager needs a launch-grade PRD for a new consumer app feature. The Skill runs discovery, drafts the PRD with numbered FRs and user journeys, runs rubric and adversarial reviews, and finalizes the document with an assumptions index. ## Quick Start Ask the assistant to help you create a PRD for your product idea and answer its discovery questions.

Frequently Asked Questions about bmad-prd

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a PRD with an AI assistant?▼

Invoke the skill with your product idea and it runs a discovery phase: brain dump, stakes calibration, and a choice between Fast path (batched questions, then a full draft) or Coaching path (section-by-section collaboration). The result is a structured PRD with numbered functional requirements and user journeys.

How do I validate an existing PRD for quality?▼

Use the Validate intent, which critiques the PRD without changing it. A rubric walker assesses seven dimensions such as decision-readiness and done-ness clarity, and findings are synthesized into HTML and Markdown validation reports.

Can the PRD workflow run headless without user interaction?▼

Yes. Headless mode accepts an intent and inputs from the caller, completes the work without prompting, and returns a JSON status payload with artifact paths, assumptions, and open questions. Ambiguous intent halts with a blocked status.

What PRD template structure does it use?▼

The default template is an Essential Spine covering vision, target user, glossary, features with globally numbered FRs, non-goals, MVP scope, success metrics, open questions, and an assumptions index. An Adapt-In Menu adds sections for compliance, enterprise, developer products, or hardware as needed.

Can I customize the PRD workflow for my organization?▼

Yes. A customize.toml file controls activation steps, persistent facts, templates, validation rubrics, document standards, external sources, and handoffs. Team and personal override TOML files merge with the base configuration per BMad rules.