bmad-validate-prd

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

Updated Aug 3, 2026
One-click install
npx skills add https://github.com/shaahy/quicknav-desktop --skill bmad-validate-prd-shaahy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-validate-prd
Source: https://github.com/shaahy/quicknav-desktop/tree/main/A%20%E6%95%99%E7%A8%8B%E9%9B%86%E5%90%88/BMAD-METHOD%E6%8A%80%E8%83%BD%E9%80%9F%E6%9F%A5/source-v6.10.0/src/bmm-skills/2-plan-workflows/bmad-validate-prd
Command: npx skills add https://github.com/shaahy/quicknav-desktop --skill bmad-validate-prd-shaahy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Existing projects and custom override files still reference the retired bmad-validate-prd skill by name; this compatibility shim keeps those invocations working while the skill is phased out in favor of bmad-prd. ## Core Features & Use Cases - Backward Compatibility: Resolves legacy bmad-validate-prd.toml and bmad-validate-prd.user.toml customization overrides so existing configurations keep working. - Deprecation Notice: Emits a localized warning telling users to migrate their customization files to bmad-prd.toml before the skill is removed in v7. - Intent Forwarding: Invokes bmad-prd with validate intent, passing pre-resolved legacy fields (activation steps, persistent facts, on_complete) and the original user input verbatim. - Use Case: A team with an older BMAD installation runs bmad-validate-prd on their PRD; the shim loads their saved overrides, warns about deprecation, and hands off validation to the consolidated bmad-prd workflow. ## Quick Start Invoke bmad-validate-prd with the path to your PRD document and it will forward the validation request to bmad-prd while applying your legacy customization overrides.

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 BMAD after bmad-validate-prd was deprecated?▼

Invoke bmad-prd directly; it detects validate intent from the conversation automatically. The deprecated bmad-validate-prd skill still works but simply forwards your request to bmad-prd with validate intent.

What happens to my bmad-validate-prd.toml customization file?▼

The shim still resolves legacy fields (activation_steps_prepend, activation_steps_append, persistent_facts, on_complete) from bmad-validate-prd.toml. Migrate it to _bmad/custom/bmad-prd.toml to silence the deprecation notice and access new fields.

When will bmad-validate-prd be removed?▼

According to its SKILL.md frontmatter, the skill is deprecated and will be removed in BMAD v7. It is retained only as a thin compatibility shim until then.

Does bmad-validate-prd perform PRD validation itself?▼

No. It performs no validation logic of its own; it resolves legacy customization, emits a deprecation notice, and hands the entire workflow to bmad-prd, which executes the validation steps.

Why do I see a deprecation notice when running PRD validation?▼

The notice appears because you invoked the legacy bmad-validate-prd name. Invoke bmad-prd directly and migrate your override file to bmad-prd.toml to silence it.