bmad-create-prd

To create a product requirements document from rough ideas, you provide conversation context and project specifics to generate a structured PRD covering scope, goals, and acceptance criteria. The skill drafts requirements directly from your input without manual assembly.

A PRD is a product requirements document defining scope, goals, and acceptance criteria for software planning. You need one when turning rough product ideas or feature definitions into structured specifications for your development workflow.

Yes, you can use existing BMad customization files when drafting a PRD. The skill resolves legacy customization configurations, loads your project context, and preserves your existing BMad setup while forwarding the creation intent to the newer bmad-prd workflow.

To generate a PRD for a new SaaS feature, ask the skill to create one and include your product ideas alongside any project-specific customization details. It processes the conversation context to produce a guided requirements document fitting your workflow.

The skill shows a deprecation notice during PRD creation because it resolves legacy customization files and then forwards the actual creation intent to the newer bmad-prd flow. This ensures workflow compatibility while transitioning you to the updated process.

The tool works best with project context and conversation input to produce a consistent document. While it can draft from rough ideas, providing project-specific customization details ensures the generated requirements fit your existing BMad setup.