bmad-create-prd

Guide stepwise creation of structured product requirements documents in Markdown.

1|Updated Dec 22, 2022
One-click install
npx skills add https://github.com/Rinzler78/osmosis-launcher --skill bmad-create-prd-rinzler78
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-create-prd
Source: https://github.com/Rinzler78/osmosis-launcher/tree/main/.agents/skills/bmad-create-prd
Command: npx skills add https://github.com/Rinzler78/osmosis-launcher --skill bmad-create-prd-rinzler78

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you create a complete product requirements document from scratch by guiding you through structured discovery, classification, scoping, and requirement definition.

Core Features & Use Cases

  • Workflow-led PRD creation: Moves step by step through discovery, vision, executive summary, success criteria, user journeys, domain requirements, innovation, project type, scoping, functional requirements, and non-functional requirements.
  • Collaborative product facilitation: Uses conversational prompts to help a product manager or founder clarify goals, users, constraints, and scope without writing the PRD all at once.
  • Document assembly and refinement: Builds the PRD incrementally, saving approved content into a structured Markdown document with workflow state tracking.
  • Use Case: You have a new product idea and want an AI assistant to help turn it into a well-structured PRD that downstream teams can use for UX, architecture, and development planning.

Quick Start

Ask the skill to help create a new product requirements document for your project.

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?

Create a product requirements document through stepwise discovery, classification, and requirement drafting using conversational prompts to clarify goals, users, constraints, and scope. This workflow builds the PRD incrementally, saving approved content into a structured Markdown document.

What is the best way to define scope and user journeys for a new software project?

Defining scope and user journeys requires guided discovery to classify project type, clarify constraints, and map functional requirements step by step. This approach ensures both vision and measurable success criteria are established before drafting the final document.

Can I use guided discovery to build a PRD for an existing software project?

Yes, guided discovery supports both greenfield and brownfield software projects by facilitating collaborative PRD assembly. It uses workflow state tracking and iterative user review to refine vision, domain requirements, and scoping for existing codebases.

How do I structure functional and non-functional requirements for product planning?

Structure functional and non-functional requirements by moving stepwise through executive summary, success criteria, user journeys, and domain requirements. The workflow assembles these measurable requirements incrementally into a Markdown document for downstream teams.

Does PRD creation work without writing the entire document all at once?

Yes, collaborative product facilitation uses conversational prompts to help a product manager or founder clarify goals incrementally without writing the PRD all at once. Workflow state tracking saves approved content iteratively for later review.