Product Manager

Convert strategic input into a structured PRD with epics, stories, and acceptance criteria.

1|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/coco-de/bmad --skill product-manager-coco-de
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Product Manager
Source: https://github.com/coco-de/bmad/tree/main/skills/bmad/bmm/pm
Command: npx skills add https://github.com/coco-de/bmad --skill product-manager-coco-de

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Product requirements and planning can be time-consuming and error-prone without a structured framework. This skill provides a repeatable approach to capture stakeholder needs, translate them into PRDs, and ensure traceability across epics, stories, and implementation.

Core Features & Use Cases

  • Create Product Requirements Documents (PRDs) that capture functional and non-functional needs.
  • Break down requirements into epics and user stories with clear acceptance criteria.
  • Prioritize features using MoSCoW, RICE, and Kano frameworks to align with business goals.
  • Produce lightweight technical specifications for smaller initiatives and ensure traceability.

Quick Start

Begin Phase 2 planning by loading the project brief and starting the PRD workflow.

Frequently Asked Questions about Product Manager

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

FAQPage Schema
How do I create a PRD from strategic input?

To create a PRD, load your project brief to convert strategic input into a structured document capturing functional and non-functional requirements, ensuring clear traceability across epics and implementation.

How do I break down product requirements into epics and user stories?

Break down product requirements by scoping Phase 2 planning activities to generate epics and user stories with clear acceptance criteria, ensuring traceability from requirements to implementation.

What is the best way to prioritize product roadmap features?

Prioritize product roadmap features using MoSCoW, RICE, and Kano models to align epics and user stories with business goals and stakeholder needs.

Can I use this for lightweight technical specifications?

Yes, you can produce lightweight technical specifications for smaller initiatives while maintaining traceability from stakeholder needs to implementation.

What frameworks are used for product requirements prioritization?

Product requirements prioritization uses MoSCoW, RICE, and Kano models to evaluate and align epics and user stories with business goals.

Do I need a project brief to start the PRD workflow?

Yes, loading a project brief is the quick start step to begin the PRD workflow and translate stakeholder needs into structured product requirements.