bmad-validate-prd

Validates product requirements documents using a structured review workflow and actionable feedback.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams validate a product requirements document against a structured review workflow so they can catch missing requirements, unclear scope, and consistency issues before implementation.

Core Features & Use Cases

  • PRD validation: Reviews a PRD for completeness, clarity, and alignment with the intended product direction.
  • Legacy compatibility: Preserves older bmad-validate-prd invocations while forwarding the work to the consolidated bmad-prd workflow.
  • Review support: Useful when you need a disciplined pass over a draft or updated PRD before handing it to engineering or stakeholders.

Quick Start

Ask this Skill to validate your PRD and provide the document path or pasted content you want reviewed.

Frequently Asked Questions about bmad-validate-prd

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

FAQPage Schema
How do I validate a product requirements document before handing it to engineering?

To validate a product requirements document, use a structured review workflow to check for missing requirements, unclear scope, and consistency issues before implementation begins. This process catches alignment gaps early.

What is PRD scope review and when do I need it?

PRD scope review is a completeness check that evaluates requirement clarity and alignment with product direction. You need it when updating a draft or finalizing a PRD before stakeholder or engineering handoff.

Does PRD validation work with legacy bmad-validate-prd invocations?

Legacy bmad-validate-prd invocations are supported through compatibility routing that forwards the validation work to the consolidated bmad-prd workflow, preserving older commands without breaking existing automation.

What context do I need to load for consistent PRD validation behavior?

Consistent PRD validation behavior requires loaded project context, BMad customization resolution, and validate intent forwarding. This environment setup ensures the review workflow applies checks uniformly.