bmad-create-prd

Forwards legacy PRD creation 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-create-prd-hordricjr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-create-prd
Source: https://github.com/HordRicJr/Akomagni/tree/main/bmad-core/.agents/skills/bmad-create-prd
Command: npx skills add https://github.com/HordRicJr/Akomagni --skill bmad-create-prd-hordricjr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Existing projects and customization files that still reference the old bmad-create-prd skill would break after it was consolidated into bmad-prd. This compatibility shim keeps those invocations working while guiding users toward the new unified skill. ## Core Features & Use Cases - Backward Compatibility: Resolves legacy bmad-create-prd.toml customization overrides (activation steps, persistent facts, on_complete hooks) so existing project configurations keep working. - Intent Forwarding: Invokes bmad-prd with create intent, skipping its intent detection step and passing pre-resolved legacy customization values. - Deprecation Notice: Emits a localized notice explaining the migration path to bmad-prd.toml and the new customization fields available. - Use Case: A team with an existing _bmad/custom/bmad-create-prd.toml runs the old skill name after an update; the shim loads their overrides, warns them about deprecation, and seamlessly creates the PRD through the new workflow. ## Quick Start Invoke the skill by name to create a new PRD, and it will forward your request to bmad-prd with create intent while applying your legacy customization overrides.

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 older bmad-create-prd name still works but simply forwards to bmad-prd with create intent.

What happened to the bmad-create-prd skill?

It was consolidated into bmad-prd and retained only as a thin compatibility shim. It resolves your legacy customization overrides, shows a deprecation notice, and forwards the request to bmad-prd with create intent.

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

Yes, the shim resolves legacy fields like activation_steps_prepend, persistent_facts, and on_complete from bmad-create-prd.toml and passes them to bmad-prd. Migrating to bmad-prd.toml unlocks additional fields such as prd_template and validation_checklist_template.

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 fields are respected, and you gain access to new options like doc_standards, finalize_reviewers, and prd_output_path.

Does bmad-create-prd support update or validate workflows?

No, this shim always forwards with create intent only. For updating or validating PRDs, invoke bmad-prd directly, which detects the appropriate intent from the conversation context.