bmad-validate-prd

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

6|Updated Aug 29, 2026
One-click install
npx skills add https://github.com/HordRicJr/Akomagni --skill bmad-validate-prd-hordricjr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-validate-prd
Source: https://github.com/HordRicJr/Akomagni/tree/main/bmad-core/.agents/skills/bmad-validate-prd
Command: npx skills add https://github.com/HordRicJr/Akomagni --skill bmad-validate-prd-hordricjr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Existing setups that invoke bmad-validate-prd by name or rely on legacy customization files would break after the skill was merged into bmad-prd. This compatibility shim keeps those invocations working while guiding users toward the consolidated workflow. ## Core Features & Use Cases - Backward Compatibility: Resolves legacy bmad-validate-prd.toml and .user.toml overrides so existing customizations keep working. - Deprecation Notice: Informs the user in their configured language that the skill is deprecated and explains how to migrate to bmad-prd. - Intent Forwarding: Invokes bmad-prd with validate intent, passing pre-resolved legacy customization values and the original user input. - Use Case: A team with an existing _bmad/custom/bmad-validate-prd.toml runs their usual validation command; the shim applies their overrides, warns about deprecation, and hands off to the new unified PRD workflow. ## Quick Start Invoke bmad-validate-prd with the path to the PRD you want validated, and it will forward the request to bmad-prd with validate intent.

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 workflow?

Invoke bmad-prd directly with validate intent, or call the legacy bmad-validate-prd name which forwards to it. The workflow loads your config, applies customization overrides, and runs the PRD validation process.

What happened to the bmad-validate-prd skill?

It was consolidated into bmad-prd and now exists only as a compatibility shim. It still works for existing invocations but emits a deprecation notice and forwards all work to bmad-prd with validate intent.

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

Yes, the shim resolves legacy fields like activation_steps_prepend, persistent_facts, and on_complete from your existing toml file 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 `_bmad/custom/bmad-validate-prd.toml` file to `_bmad/custom/bmad-prd.toml` and invoke bmad-prd directly. The new version respects your existing fields and adds options like prd_template, validation_checklist_template, and external_sources.

Why am I seeing a deprecation notice when validating a PRD?

The notice appears because you invoked the deprecated bmad-validate-prd shim instead of bmad-prd directly. It is informational only; your validation still runs, and migrating your customization file silences it.