bmad-create-prd

Create a product requirements document via a guided stepwise workflow.

2|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/cassioalexandre/agf --skill bmad-create-prd-cassioalexandre
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-create-prd
Source: https://github.com/cassioalexandre/agf/tree/main/_bmad/bmm/2-plan-workflows/bmad-create-prd
Command: npx skills add https://github.com/cassioalexandre/agf --skill bmad-create-prd-cassioalexandre

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you turn an early product idea into a complete, information-dense PRD starting from zero, using a structured workflow that prevents skipped steps and ensures the output is suitable for both humans and downstream LLM/engineering use.

Core Features & Use Cases

  • PRD workspace initialization: Creates a PRD document from the template and discovers any user-confirmed input documents (briefs, research, project context).
  • Facilitated PRD building workflow: Guides collaborative elicitation of classification, vision, executive summary, success criteria, journeys, requirements, and scope.
  • Capability-contract outputs: Produces FRs (what the product must do) and NFRs (quality attributes) to bind downstream UX/architecture/epics work.
  • Resume-friendly: Detects continuation state and resumes without redoing completed steps.

Quick Start

Ask an AI agent to run the bmad-create-prd workflow to create a new PRD workspace and draft the full PRD based on your answers.

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 product requirements document from scratch using an AI agent?▼

To create a product requirements document (PRD) from scratch, an AI agent uses a guided stepwise workflow that initializes a workspace and elicits your inputs before drafting the executive summary, success criteria, and requirements.

What is a capability contract in a PRD and why is it needed?▼

A capability contract in a PRD defines functional and non-functional requirements to bind downstream UX, architecture, and engineering work, ensuring the product requirements document is suitable for both human and LLM execution.

Can I resume a PRD generation workflow if I stop halfway through?▼

Yes, the PRD generation workflow detects continuation state and resumes automatically, skipping completed steps so you can continue drafting your product requirements document without redoing previous inputs.

How do I ensure my PRD includes user journeys and scope without skipping sections?▼

You ensure your PRD includes user journeys and scope by using a facilitated governance workflow that enforces sequential step execution and user-gated menus, preventing skipped sections during document automation.

What's the best way to turn early product ideas into information-dense requirements?▼

The best way to turn early ideas into dense requirements is using collaborative elicitation to gather project context and briefs, structuring them into a polish-ready PRD artifact with clear scoping and quality attributes.

Do I need prior research briefs to start drafting a PRD?▼

No, you do not need prior research briefs to start drafting a PRD, but the workflow discovers and integrates any user-confirmed input documents like briefs or research to enrich the final product requirements output.