bmad-product-planning_skill

Overview

This skill converts validated discovery insights into a production-ready Product Requirements Document (PRD) and an epic roadmap. It aligns stakeholders, captures constraints and acceptance criteria, and prepares the project for architecture, UX, and delivery teams. The outputs are written to the project docs folder and summarized for the requestor.

How this skill works

The skill first validates readiness against a checklist and ensures required inputs (business goal, stakeholders, constraints, discovery artifacts) are present. It extracts goals, scope, constraints, and success metrics from discovery artifacts, then maps them into a PRD and a prioritized epic roadmap following templated structures. If structured data exists, it runs an automation script to generate files; otherwise it composes the documents manually and applies quality gates before delivery.

When to use it

• You have completed discovery and need a formal PRD for Level 2-4 projects.
• You need a prioritized epic roadmap and acceptance signals for delivery.
• You want to align stakeholders and capture approvals or open concerns.
• You must translate validated research into developer-ready requirements.
• You need to prepare for downstream architecture, UX, or sprint planning.

Best practices

• Provide a clear business_goal with measurable success metrics before invoking the skill.
• Attach all discovery_artifacts (briefs, research memos, interview notes) and flag any gaps.
• List stakeholders with decision roles and known approvals or objections.
• Declare constraints early (technical, regulatory, budget, timeline) to shape scope.
• Address checklist items and resolve contradictions before generating the final PRD.

Example use cases

• Create a PRD and epic roadmap for a new mobile onboarding flow after user research is complete.
• Turn validated discovery for a payments integration into acceptance criteria and prioritized epics.
• Generate delivery-ready PRD docs and a release-sequenced epic list for a cross-team feature.
• Refine scope and constraints into a clear project brief to hand off to architecture and UX.