bmad-create-prd

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? This Skill preserves backward compatibility for users and automation that still invoke the retired bmad-create-prd command, ensuring existing customization files and muscle memory continue to work after the workflow was consolidated into bmad-prd. ## Core Features & Use Cases - Deprecation Forwarding: Routes every invocation to bmad-prd with create intent, skipping the new workflow's intent detection step. - Legacy Customization Resolution: Loads bmad-create-prd.toml and bmad-create-prd.user.toml overrides (activation steps, persistent facts, on_complete) and passes them to bmad-prd so old configurations keep working. - Migration Guidance: Emits a localized deprecation notice explaining how to migrate customization files to bmad-prd.toml and unlock the expanded customization surface. - Use Case: A team with an existing _bmad/custom/bmad-create-prd.toml override invokes the old skill name; the shim resolves their overrides, warns them once, and hands off to bmad-prd without breaking their PRD creation flow. ## Quick Start Invoke bmad-create-prd as before and it will notify you of the deprecation, then automatically run the bmad-prd workflow in create mode with your legacy customizations applied.

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 Method after bmad-create-prd was deprecated?

Invoke bmad-prd directly instead of bmad-create-prd. The consolidated workflow detects create, update, or validate intent from the conversation, so no separate create command is needed.

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

Yes, the shim resolves bmad-create-prd.toml and bmad-create-prd.user.toml overrides for the legacy fields (activation_steps_prepend, activation_steps_append, persistent_facts, on_complete) and passes them to bmad-prd. Migrating to bmad-prd.toml unlocks additional fields.

What new customization options does bmad-prd support?

Beyond the legacy fields, bmad-prd supports prd_template, validation_checklist_template, validation_report_template, doc_standards, finalize_reviewers, external_sources, external_handoffs, prd_output_path, and run_folder_pattern.

How do I silence the bmad-create-prd deprecation notice?

Migrate your overrides from _bmad/custom/bmad-create-prd.toml to _bmad/custom/bmad-prd.toml and invoke bmad-prd directly. The notice only appears when the deprecated shim is invoked.

When should I stop using bmad-create-prd entirely?

Stop using it as soon as practical, since it is deprecated and will be removed in a future release. It exists only as a compatibility shim; all new PRD work should go through bmad-prd.