bmad-validate-prd

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

Updated Sep 3, 2026
One-click install
npx skills add https://github.com/watchthelight/shatterfish --skill bmad-validate-prd-watchthelight
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-validate-prd
Source: https://github.com/watchthelight/shatterfish/tree/main/.claude/skills/bmad-validate-prd
Command: npx skills add https://github.com/watchthelight/shatterfish --skill bmad-validate-prd-watchthelight

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? This Skill preserves backward compatibility for existing invocations of the retired bmad-validate-prd workflow, ensuring legacy commands and customization files continue to work after the workflow was consolidated into bmad-prd. ## Core Features & Use Cases - Deprecation Forwarding: Emits a deprecation notice and delegates all work to bmad-prd with validate intent pre-set, skipping intent detection. - Legacy Customization Resolution: Resolves overrides from _bmad/custom/bmad-validate-prd.toml (activation steps, persistent facts, on_complete) and passes them to bmad-prd so existing configurations keep working. - Use Case: A team that previously ran bmad-validate-prd to check PRD quality can keep using the same command and TOML override files while migrating to bmad-prd at their own pace. ## Quick Start Invoke bmad-validate-prd with the path to your PRD document and it will forward the request to bmad-prd for validation.

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, or invoke the legacy bmad-validate-prd name which forwards to bmad-prd automatically. The workflow loads validation checklists and produces a validation report for your PRD document.

What happened to the bmad-validate-prd skill?

It was consolidated into bmad-prd and now exists only as a compatibility shim. It emits a deprecation notice, resolves legacy customization overrides, and delegates all validation work to bmad-prd with validate intent.

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

Yes, the shim resolves legacy fields (activation_steps_prepend, activation_steps_append, persistent_facts, on_complete) from 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 _bmad/custom/bmad-validate-prd.toml file to bmad-prd.toml and invoke bmad-prd directly. Existing field values are respected, and you gain access to new options like prd_template, validation_checklist_template, and prd_output_path.

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

The notice appears because the skill is deprecated and scheduled for removal in a future release. It informs you that the invocation now forwards to bmad-prd and explains how to migrate your customization file to silence the notice.