bmad-product-planning

Generate PRD.md and epics.md from validated discovery insights.

67|11|Updated Oct 28, 2025
One-click install
npx skills add https://github.com/bacoco/BMad-Skills --skill bmad-product-planning
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-product-planning
Source: https://github.com/bacoco/BMad-Skills/tree/main/.claude/skills/bmad-product-planning
Command: npx skills add https://github.com/bacoco/BMad-Skills --skill bmad-product-planning

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and assets (resource) components.

What problem does it solve?

This skill converts validated discovery inputs into a production-ready Product Requirements Document (PRD) and an epic roadmap.

Core Features & Use Cases

  • PRD generation: goals, background, FR/NFR, journeys, KPIs.
  • Epic roadmap: sequencing and dependencies.
  • Traceability: links PRD requirements to epics and stories.

Quick Start

Provide discovery artifacts and run the PRD generator to produce PRD.md and epics.md using templates in assets/.

Frequently Asked Questions about bmad-product-planning

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a product requirements document (PRD) from discovery insights?

PRD generation converts validated discovery artifacts into a production-ready Product Requirements Document by applying structured templates. The Skill automates PRD creation with goals, background, functional and non-functional requirements, user journeys, and KPIs, validating inputs via checklist and outputting PRD.md to your documentation repository.

What's included in an epic roadmap and how do I sequence features across it?

An epic roadmap organizes features into sequenced epics with explicit dependencies and traceability links back to PRD requirements. The Skill generates epics.md showing feature ordering, dependencies between epics, and connections to individual stories, enabling stakeholders to understand prioritization and delivery phases.

Can I link requirements to epics and stories for traceability?

Yes. Traceability is built into the Skill's output—PRD requirements map directly to epics and downstream stories. This ensures every requirement has a tracked path through planning to implementation, making it easier to validate coverage and manage scope across stakeholders and disciplines.

What discovery inputs do I need before generating a PRD and roadmap?

You need validated discovery artifacts—research findings, user insights, business goals, and scope definition. The Skill includes a CHECKLIST.md that validates these inputs before processing. Once validated, the templates in assets/ generate your PRD.md and epics.md outputs.

Is this approach suitable for large, multi-phase product initiatives?

Yes. The Skill is designed for Level 2–4 product initiatives requiring structured planning across multiple teams and disciplines. It handles complex roadmaps with sequenced epics, stakeholder alignment, and cross-functional traceability, making it suitable for phased rollouts and dependent features.

What happens if my discovery inputs are incomplete or don't meet requirements?

The CHECKLIST.md validation step flags missing or incomplete inputs before PRD generation begins, preventing downstream rework. You address gaps in discovery artifacts first, then re-run the generator to produce valid, traceable PRD and epic artifacts.