bmad-agent-pm

Generate and refine Product Requirements Documents from discovery interviews and stakeholder alignment.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/amitmishra-byldd/Bmad-Note-Maker --skill bmad-agent-pm-amitmishra-byldd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-agent-pm
Source: https://github.com/amitmishra-byldd/Bmad-Note-Maker/tree/main/_bmad/bmm/2-plan-workflows/bmad-agent-pm
Command: npx skills add https://github.com/amitmishra-byldd/Bmad-Note-Maker --skill bmad-agent-pm-amitmishra-byldd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a product manager persona that leads focused discovery, turns ambiguous product ideas into validated Product Requirements Documents (PRDs), and aligns stakeholders so teams build the smallest thing that validates critical assumptions.

Core Features & Use Cases

  • Interview-driven PRD creation: Facilitate user interviews and synthesize findings into a structured PRD.
  • Validation and editing: Validate existing PRDs for completeness, clarity, and alignment with user needs and technical constraints.
  • Delivery artifacts: Produce epics and stories, check implementation readiness, and recommend corrective actions during mid-stream changes.
  • Use Case: Run a discovery session to convert stakeholder goals and interview insights into a prioritized, implementable PRD with epics and acceptance criteria.

Quick Start

Activate John by asking: "Hi John, help me create a PRD for [project name] and start by generating user interview questions and core assumptions to validate."

Frequently Asked Questions about bmad-agent-pm

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

FAQPage Schema
How do I create a PRD from user interviews and stakeholder goals?

To create a PRD from user interviews, facilitate targeted discovery sessions to extract core assumptions, synthesize the findings, and structure them into a validated document with prioritized epics and acceptance criteria.

What is the best way to validate existing product requirements for alignment?

Validating product requirements involves checking existing PRDs for completeness and clarity, ensuring alignment between user needs and technical constraints, and verifying that stakeholders agree on the smallest build to test critical assumptions.

How do I generate epics and user stories from a product strategy?

Generate epics and user stories by translating a validated PRD into actionable delivery artifacts, checking implementation readiness, and defining clear acceptance criteria for B2B or consumer product development.

Can I use interview-driven requirements discovery for mid-stream product changes?

Yes, interview-driven requirements discovery supports mid-stream changes by validating new assumptions, updating the PRD, and recommending corrective actions to keep epics and stories aligned with the product strategy.

What do I need to start structured PRD creation and stakeholder alignment?

To start structured PRD creation, you need a defined project goal and a willingness to run discovery interviews, which the skill uses to elicit requirements and perform stakeholder alignment checks.