bmad-create-prd

To create a product requirements document from scratch, this workflow facilitates step-by-step initialization, discovery, and drafting with explicit review and approval gates for each section. It translates product discovery into a complete capability contract.

A capability contract is the final PRD output that translates product discovery into traceable, measurable functional requirements. It supports defining SMART success criteria and narrative user journeys for downstream implementation planning.

Yes, you can generate user journeys and SMART success criteria as part of the structured PRD sections. The workflow supports defining narrative user journeys alongside capability-based functional requirements with user-approval checkpoints.

Yes, the PRD output produces a human-readable document with an LLM-friendly structure designed specifically for downstream UX, architecture, epics, and implementation planning. It serves dual audiences for human review and agent work.

You can add domain-specific requirements through optional domain and innovation depth configurations during the workflow. The system includes domain-specific requirements and innovation analysis driven by project-type customization when applicable.

The best way to structure a PRD for enterprise AI projects is using a structured PM workflow that generates sections with user-approval checkpoints. This approach ensures deterministic activation via resolver-based customization loading for varied project types.