bmad-validate-prd

Redirect deprecated bmad-validate-prd calls to bmad-prd with fallback configuration.

1|Updated May 31, 2026
One-click install
npx skills add https://github.com/sfines/slf-llm-wiki-py --skill bmad-validate-prd-sfines
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-validate-prd
Source: https://github.com/sfines/slf-llm-wiki-py/tree/main/.agents/skills/bmad-validate-prd
Command: npx skills add https://github.com/sfines/slf-llm-wiki-py --skill bmad-validate-prd-sfines

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures backwards compatibility with previously deployed versions of a workflow that has been consolidated under the bmad-prd skill.

Core Features & Use Cases

  • Deprecation Transition: Acts as a compatibility layer, redirecting calls from the deprecated bmad-validate-prd to the updated bmad-prd skill.
  • Customization Support: Picks up existing custom configurations while deprecating outdated fields.
  • Notice Emission: Issues a notice about deprecation, with a suggestion for migration to the updated skill.

Quick Start

Execute the bmad-validate-prd skill to validate the PRD as previously done. Note: New customizations should use the bmad-prd skill directly.

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 after the bmad-validate-prd skill has been deprecated?

To validate a PRD after deprecation, execute the bmad-validate-prd skill as previously done. It acts as a compatibility layer, automatically redirecting your validation intent to the updated bmad-prd skill while emitting a migration notice.

What happens to my existing custom configurations when transitioning to bmad-prd?

When transitioning to bmad-prd, your existing custom configurations are picked up and preserved. The compatibility layer handles deprecated fields by providing fallbacks from previous configuration overrides during the redirection process.

Why does the bmad-validate-prd skill issue a deprecation notice?

The deprecation notice is emitted because the workflow has been consolidated under the bmad-prd skill. It informs you of the deprecation and suggests migrating directly to bmad-prd for any new customizations going forward.

Can I use bmad-validate-prd without the bmad-prd skill installed?

No, you cannot use bmad-validate-prd without bmad-prd. The compatibility layer assumes the presence of the bmad-prd skill to provide the required intent context for processing the redirected validation requests.

When should I use bmad-validate-prd versus migrating to bmad-prd directly?

Use bmad-validate-prd only for maintaining backwards compatibility with previously deployed workflows. For all new customizations and validation tasks, you should use the updated bmad-prd skill directly to avoid relying on deprecated fields.