bmad-pm

Generate product briefs, PRDs, and feature documents with prioritization frameworks.

2|Updated Apr 21, 2025
One-click install
npx skills add https://github.com/akvo/akvo-rag --skill bmad-pm-akvo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-pm
Source: https://github.com/akvo/akvo-rag/tree/main/.agent/skills/bmad-pm
Command: npx skills add https://github.com/akvo/akvo-rag --skill bmad-pm-akvo

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines the creation of product documentation, from initial product briefs to detailed PRDs, ensuring clear communication and alignment across teams.

Core Features & Use Cases

  • Product Brief Generation: Define problem statements, target users, value propositions, and success metrics.
  • PRD Creation: Elicit requirements, map user journeys, and define functional/non-functional specifications.
  • Feature Documentation: Create detailed documents for specific features, including user stories and requirements.
  • Competitive Analysis: Research and analyze competitors to identify market gaps and opportunities.
  • Feature Prioritization: Employ frameworks like MoSCoW and RICE to prioritize product backlogs.
  • Stakeholder Workshops: Facilitate collaborative discovery sessions to gather project context and define MVP scope.

Quick Start

Use the bmad-pm skill to create a product brief for a new mobile budgeting app.

Frequently Asked Questions about bmad-pm

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

FAQPage Schema
How do I prioritize product features using MoSCoW and RICE frameworks?

Feature prioritization uses MoSCoW and RICE frameworks to structure your product backlog. These methods help quantify feature value, urgency, and effort, ensuring objective alignment on MVP scope definition.

Can I use stakeholder workshops to define MVP scope and user journeys?

Competitive analysis for product management involves researching competitors to identify market gaps and opportunities. This process generates artifacts that define your product vision and differentiate your value proposition in the market.

What should be included in a product brief for a new software application?

Yes, stakeholder workshops facilitate collaborative discovery sessions to gather project context, define MVP scope, and map user journeys. These sessions align team understanding and generate detailed feature documentation.

Does product documentation generation support feature documentation with user stories?

A product brief should include problem statements, target users, value propositions, and success metrics. These components establish foundational alignment and streamline communication across product and engineering teams.

Why does feature prioritization matter when defining MVP scope?

Yes, product documentation generation creates detailed documents for specific features, including user stories and requirements. This bridges high-level product strategy with granular engineering execution.