bmad-agent-pm

Drive PRD creation through structured user interviews and stakeholder alignment.

4|1|Updated Sep 30, 2024
One-click install
npx skills add https://github.com/co-cddo/ndx --skill bmad-agent-pm-co-cddo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-agent-pm
Source: https://github.com/co-cddo/ndx/tree/main/_bmad/bmm/2-plan-workflows/bmad-agent-pm
Command: npx skills add https://github.com/co-cddo/ndx --skill bmad-agent-pm-co-cddo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Product teams often struggle to convert ambiguous stakeholder requests into a concrete, testable PRD. This skill provides a Product Manager persona who drives PRD creation through structured user interviews, requirements discovery, and stakeholder alignment, helping to rapidly validate assumptions and reduce scope creep.

Core Features & Use Cases

  • Structured user interviews to surface real needs and verify assumed requirements.
  • PRD drafting and stakeholder alignment to ensure cross-functional buy-in.
  • Lean validation cycle that ships the smallest thing that proves or disproves an assumption.

Quick Start

Begin by identifying the user problem and start interviews to draft a lean PRD that validates the core assumption.

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 ambiguous stakeholder requests?

PRD creation from ambiguous requests requires structured user interviews to surface real needs, define scope, align stakeholders, and validate assumptions with measurable criteria to reduce scope creep.

What is lean PRD validation and how does it work?

Lean PRD validation ships the smallest product increment to prove or disprove a core assumption, using targeted user interviews and measurable criteria to rapidly test requirements before committing to full delivery.

How do I align stakeholders to product requirements?

Stakeholder alignment to product requirements is achieved by drafting a PRD grounded in real user needs from structured interviews, then coordinating cross-functional delivery around a clear, measurable outcome.

Can I use user interviews to discover product requirements?

User interviews can discover product requirements by surfacing real user needs and verifying assumed requirements, providing the foundation for a lean PRD and cross-functional stakeholder alignment.

What's the best way to reduce scope creep during product discovery?

Reducing scope creep during product discovery involves structured user interviews to validate assumptions, drafting a lean PRD with measurable criteria, and aligning stakeholders to a clear outcome before delivery.

When do I need structured requirements discovery for my roadmap?

Structured requirements discovery is needed when converting ambiguous stakeholder requests into a testable PRD, ensuring roadmap items reflect real user needs validated through interviews and measurable criteria.