bmad-validate-prd

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

Updated Jul 2, 2026
One-click install
npx skills add https://github.com/tuanpa-nhg-eng/nhg-ipms --skill bmad-validate-prd-tuanpa-nhg-eng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-validate-prd
Source: https://github.com/tuanpa-nhg-eng/nhg-ipms/tree/main/.claude/skills/bmad-validate-prd
Command: npx skills add https://github.com/tuanpa-nhg-eng/nhg-ipms --skill bmad-validate-prd-tuanpa-nhg-eng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? This Skill keeps existing invocations of the deprecated bmad-validate-prd command working after its functionality was merged into bmad-prd, so legacy customization files and muscle memory do not break. ## Core Features & Use Cases - Backward Compatibility Shim: Resolves legacy customization overrides from _bmad/custom/bmad-validate-prd.toml and forwards them to bmad-prd. - Deprecation Notice: Emits a localized notice explaining the migration path to bmad-prd and its expanded customization surface. - Use Case: A team with an existing bmad-validate-prd.toml override invokes the old skill name; the shim loads their persistent facts and activation steps, warns about deprecation, and runs the PRD validation workflow through bmad-prd with validate intent. ## Quick Start Invoke bmad-validate-prd with the path to your PRD document to run the validation workflow through the consolidated 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 your PRD path; it detects validate intent from the conversation. The deprecated bmad-validate-prd name still works but forwards to bmad-prd and shows a deprecation notice.

Is bmad-validate-prd deprecated and what replaces it?

Yes, bmad-validate-prd is deprecated and will be removed in a future release. It is replaced by bmad-prd, which handles create, update, and validate intents in one consolidated workflow.

Will my bmad-validate-prd.toml customization file still work?

Yes, the shim resolves legacy fields like activation_steps_prepend, persistent_facts, and on_complete from _bmad/custom/bmad-validate-prd.toml and passes them to bmad-prd. Migrating to bmad-prd.toml unlocks additional customization fields.

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

Rename your override file from _bmad/custom/bmad-validate-prd.toml to _bmad/custom/bmad-prd.toml and invoke bmad-prd directly. Existing fields are respected, and new fields like prd_template and validation_checklist_template become available.

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

The notice appears because the skill is a compatibility shim retained for legacy invocations. It informs you that the skill now forwards to bmad-prd and explains how to migrate your customization file to silence the notice.