bmad-validate-prd

Forwards legacy PRD validation invocations to the bmad-prd validate workflow.

Updated Jun 3, 2026
One-click install
npx skills add https://github.com/MathematicGuy/team-006-vin20k --skill bmad-validate-prd-mathematicguy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-validate-prd
Source: https://github.com/MathematicGuy/team-006-vin20k/tree/main/.agent/skills/bmad-validate-prd
Command: npx skills add https://github.com/MathematicGuy/team-006-vin20k --skill bmad-validate-prd-mathematicguy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? This Skill preserves backward compatibility for teams still invoking the deprecated bmad-validate-prd command, ensuring existing customizations and override files continue to work while routing all validation work to the consolidated bmad-prd workflow. ## Core Features & Use Cases - Deprecation Shim: Emits a migration notice and forwards the invocation to bmad-prd with validate intent, skipping its intent detection step. - Customization Resolution: Loads legacy override files (bmad-validate-prd.toml and .user.toml) for activation steps, persistent facts, and on-complete behavior, then passes them to bmad-prd. - Use Case: A team with an existing _bmad/custom/bmad-validate-prd.toml configuration invokes the old skill name; the shim resolves their customizations, warns about deprecation, and runs the PRD validation through bmad-prd without breaking their workflow. ## Quick Start Invoke bmad-validate-prd with the path to your PRD document to run the validation workflow through the forwarded bmad-prd skill.

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 with the BMad method?▼

Invoke bmad-prd directly with validate intent, passing the path to your PRD document. The deprecated bmad-validate-prd skill still works but simply forwards to bmad-prd after resolving legacy customizations.

What happened to the bmad-validate-prd skill?▼

It was consolidated into bmad-prd and retained as a thin compatibility shim. It will be removed in v7, so new work should invoke bmad-prd directly, which detects create, update, and validate intent automatically.

Will my bmad-validate-prd.toml customizations still work?▼

Yes, legacy fields like activation_steps_prepend, activation_steps_append, persistent_facts, and on_complete are resolved and passed to bmad-prd. Migrating the file to bmad-prd.toml unlocks additional fields like prd_template and validation_checklist.

How do I migrate from bmad-validate-prd to bmad-prd?▼

Rename your _bmad/custom/bmad-validate-prd.toml file to _bmad/custom/bmad-prd.toml and invoke bmad-prd directly. This silences the deprecation notice and exposes the full new customization surface including output_dir and external_sources.

Why does bmad-validate-prd show a deprecation notice?▼

The notice appears because the skill is scheduled for removal in v7 and now only forwards to bmad-prd. It is displayed in your configured communication language and can be silenced by migrating to bmad-prd.