bmad-validate-prd

Validate product requirement documents by forwarding requests to bmad-prd.

1|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/mol4/BMAD-Board --skill bmad-validate-prd-mol4
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-validate-prd
Source: https://github.com/mol4/BMAD-Board/tree/main/BMAD%20board/.agents/skills/bmad-validate-prd
Command: npx skills add https://github.com/mol4/BMAD-Board --skill bmad-validate-prd-mol4

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill keeps older PRD validation workflows working while BMAD transitions to the newer bmad-prd workflow, so existing prompts and overrides still succeed without breaking.

Core Features & Use Cases

  • Legacy Compatibility: Preserves the old bmad-validate-prd entry point for existing automations and user habits.
  • PRD Validation Handoff: Loads BMAD configuration and forwards the request to bmad-prd with validate intent.
  • Migration Guidance: Surfaces the deprecation notice and points users toward the modern bmad-prd customization surface.
  • Use Case: A team with saved shortcuts or custom overrides can keep validating PRDs today while gradually migrating to the new workflow.

Quick Start

Ask the assistant to validate your PRD with this skill so it loads the BMAD config, shows the deprecation notice, and forwards the request to bmad-prd.

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 PRD for a BMAD workflow?

PRD validation for BMAD workflows is handled by loading the BMAD configuration and forwarding the request to the newer bmad-prd workflow with a validate intent. This process checks your document against current requirements.

Why does my bmad-validate-prd invocation show a deprecation notice?

A deprecation notice appears because bmad-validate-prd is a legacy compatibility shim. It keeps older automations running while pointing users to transition to the modern bmad-prd customization surface.

Can I use bmad-validate-prd with my existing saved shortcuts?

Yes, bmad-validate-prd maintains legacy compatibility so existing saved shortcuts and custom overrides continue to succeed without breaking. This allows teams to keep validating PRDs while gradually migrating.

What is the best way to migrate from bmad-validate-prd to the new workflow?

The best way to migrate is to follow the deprecation notice surfaced by bmad-validate-prd and transition your custom overrides to the modern bmad-prd customization surface. This enables gradual migration without breaking existing automations.

Do I need to resolve BMAD customization before validating my PRD?

Validating your PRD requires BMAD customization resolution and configuration loading. The skill processes these prerequisites before forwarding the original user intent to bmad-prd with a validate intent.