bmad-prd

Create, update, and validate product requirements documents for BMad-driven workflows.

Updated May 23, 2026
One-click install
npx skills add https://github.com/diegosanchespereira1/lavarapido --skill bmad-prd-diegosanchespereira1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-prd
Source: https://github.com/diegosanchespereira1/lavarapido/tree/main/lava-rapido/.agents/skills/bmad-prd
Command: npx skills add https://github.com/diegosanchespereira1/lavarapido --skill bmad-prd-diegosanchespereira1

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

BMad PRD turns early product ideas, updates, and critique requests into structured PRDs with enough rigor for downstream design, architecture, and story-writing work. It helps teams avoid vague scope, missing decisions, and inconsistent requirements by keeping a decision log, assumptions index, and review loop in one workflow.

Core Features & Use Cases

  • Create PRDs: Start a new PRD from a brief, notes, or source documents and guide discovery, scope, and finalization.
  • Update PRDs: Reconcile an existing PRD against change signals, conflicts, and new inputs while preserving the decision trail.
  • Validate PRDs: Critique an existing PRD against a quality rubric and generate a validation report for review.
  • Use Case: A product manager has a rough feature brief and needs a decision-ready PRD that downstream UX and engineering teams can trust.

Quick Start

Use the bmad-prd skill to turn your product brief or existing PRD into a clear, validated requirements document.

Frequently Asked Questions about bmad-prd

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

FAQPage Schema
How do I draft a product requirements document from a rough feature brief?

To draft a product requirements document (PRD) from a feature brief, the tool extracts source inputs, guides scope discovery, logs decisions, and finalizes the output for downstream teams.

What is the best way to validate an existing PRD against a quality rubric?

Validating a PRD requires critiquing the existing document against a structured quality rubric, which then generates a validation report to guide the review workflow and ensure requirements consistency.

How do I update a PRD when new change signals and inputs are introduced?

Updating a PRD involves reconciling the existing document against new inputs and conflicts while preserving the decision trail, ensuring that original assumptions and decisions remain logged.

Why does my PRD review workflow fail to capture scope decisions and assumptions?

PRD review workflows often fail when missing a structured decision log and assumptions index, which this tool integrates to prevent vague scope and inconsistent requirements during drafting.

Can I use this PRD drafting approach for internal software product initiatives?

Yes, this PRD drafting and validation workflow applies directly to internal software product initiatives, ensuring structured extraction of source inputs and decision-ready handoff.

Do I need a special framework to use this product management validation workflow?

This validation workflow is designed for BMad-driven workflows, requiring structured source inputs to generate decision-ready product requirements documents for downstream design and architecture.