bmad-validate-prd

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

Updated Aug 25, 2024
One-click install
npx skills add https://github.com/LeGeRyChEeSe/LanPlay-DiscordBot --skill bmad-validate-prd-legerycheese
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-validate-prd
Source: https://github.com/LeGeRyChEeSe/LanPlay-DiscordBot/tree/main/bmad/src/bmm-skills/2-plan-workflows/bmad-validate-prd
Command: npx skills add https://github.com/LeGeRyChEeSe/LanPlay-DiscordBot --skill bmad-validate-prd-legerycheese

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? This Skill preserves backward compatibility for existing invocations of the deprecated bmad-validate-prd workflow by transparently forwarding them to the consolidated bmad-prd skill. ## Core Features & Use Cases - Deprecation Shim: Emits a deprecation notice and routes validation requests to bmad-prd with validate intent, skipping its intent detection step. - Legacy Customization Support: Resolves legacy override fields (activation_steps_prepend, activation_steps_append, persistent_facts, on_complete) from _bmad/custom/bmad-validate-prd.toml files so existing configurations keep working. - Use Case: A team with an existing bmad-validate-prd.toml customization file invokes the old skill name; the shim loads their overrides, warns about deprecation, and hands off to bmad-prd to validate the target PRD. ## Quick Start Invoke bmad-validate-prd with the path to your PRD document to run validation through the forwarded bmad-prd workflow.

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 your request to bmad-prd after showing a deprecation notice.

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

Yes, bmad-validate-prd is deprecated and will be removed in v7. It is replaced by bmad-prd, which detects create, update, and validate intent automatically from the conversation.

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

Yes, legacy fields like activation_steps_prepend, activation_steps_append, persistent_facts, and on_complete are still resolved and passed to bmad-prd. Migrating the file to bmad-prd.toml unlocks additional customization fields such as 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.

What are the limitations of the bmad-validate-prd shim?▼

The shim only supports the four legacy customization fields and cannot use new options like validation_checklist, doc_standards, or external_sources. It is a temporary compatibility layer scheduled for removal in v7.