bmad-create-prd

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

Updated Jul 2, 2026
One-click install
npx skills add https://github.com/tuanpa-nhg-eng/nhg-ipms --skill bmad-create-prd-tuanpa-nhg-eng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-create-prd
Source: https://github.com/tuanpa-nhg-eng/nhg-ipms/tree/main/.claude/skills/bmad-create-prd
Command: npx skills add https://github.com/tuanpa-nhg-eng/nhg-ipms --skill bmad-create-prd-tuanpa-nhg-eng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? This Skill preserves backward compatibility for existing invocations of the deprecated bmad-create-prd command, ensuring old workflows and customization files continue to function after consolidation into bmad-prd. ## Core Features & Use Cases - Deprecation Forwarding: Redirects all create-PRD requests to the bmad-prd skill with create intent pre-set, skipping intent detection. - Legacy Customization Support: Resolves overrides from _bmad/custom/bmad-create-prd.toml files, including activation steps, persistent facts, and completion hooks. - Migration Guidance: Emits a deprecation notice explaining how to migrate customization files to the new bmad-prd format. - Use Case: A team with existing automation calling bmad-create-prd can continue operating without breaking changes while planning their migration to bmad-prd. ## Quick Start Invoke bmad-create-prd with your PRD requirements and it will forward the request to bmad-prd with a deprecation notice.

Frequently Asked Questions about bmad-create-prd

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a PRD with the BMad framework?

Invoke the bmad-prd skill directly, which detects create, update, or validate intent from your conversation. The legacy bmad-create-prd skill still works but forwards to bmad-prd and displays a deprecation notice.

What happened to the bmad-create-prd skill?

It was consolidated into bmad-prd and retained as a thin compatibility shim. It forwards all invocations to bmad-prd with create intent while honoring legacy customization file overrides.

Will my bmad-create-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. However, migrating to bmad-prd.toml unlocks additional customization fields.

How do I migrate from bmad-create-prd to bmad-prd?

Rename your customization file from `_bmad/custom/bmad-create-prd.toml` to `_bmad/custom/bmad-prd.toml` and invoke bmad-prd directly. Existing field values carry over, and new fields like prd_template and validation_checklist_template become available.

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

The notice appears because you invoked the deprecated bmad-create-prd skill, which now forwards to bmad-prd. To silence it, migrate your customization file and call bmad-prd directly.