bmad-agent-pm

Create and manage product requirements documents through structured user interviews.

Updated May 13, 2026
One-click install
npx skills add https://github.com/Markuson/ivo_corr --skill bmad-agent-pm-markuson
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-agent-pm
Source: https://github.com/Markuson/ivo_corr/tree/main/.agents/skills/bmad-agent-pm
Command: npx skills add https://github.com/Markuson/ivo_corr --skill bmad-agent-pm-markuson

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill eliminates the friction of product requirements documentation by providing a structured, persona-driven environment for creating, validating, and maintaining PRDs and development artifacts.

Core Features & Use Cases

  • PRD Lifecycle Management: Facilitates the creation, editing, and validation of Product Requirements Documents using industry-standard methodologies.
  • Implementation Readiness: Ensures alignment between UX, architecture, and development epics to prevent scope creep and technical debt.
  • Use Case: When starting a new feature, invoke this skill to have John guide you through a structured interview process that results in a validated PRD and a prioritized list of development stories.

Quick Start

Invoke the bmad-agent-pm skill and ask John to help you create a new product requirements document for your upcoming feature.

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 product requirements document without scope creep?

Product requirements document creation without scope creep requires structured user interviews and stakeholder alignment. This skill enforces implementation readiness checks to ensure alignment between UX, architecture, and development epics before execution begins.

How does an agile PRD orchestration process work?

Agile PRD orchestration works by guiding you through a persona-driven interview process to validate requirements. It supports the full product lifecycle, generating prioritized development stories and enabling course correction during execution to prevent technical debt.

What is the best way to generate development epics from stakeholder interviews?

The best way to generate development epics from stakeholder interviews is using a structured, persona-driven environment. This approach validates product requirements and outputs a prioritized list of development stories aligned with your architecture.

Do I need project-specific customization files for product management lifecycle tracking?

Yes, you need project-specific customization files for product management lifecycle tracking. The skill requires integration with these files and adherence to defined product management principles to maintain validated PRDs and development artifacts.

How do I validate implementation readiness before starting feature development?

To validate implementation readiness before feature development, this skill checks alignment between UX, architecture, and development epics. This structured validation prevents scope creep and technical debt during the execution phase.