Product Manager

Generate comprehensive PRDs with FRs, NFRs, epics, user stories, and acceptance criteria.

Updated Dec 4, 2025
One-click install
npx skills add https://github.com/co-cddo/innovation-sandbox-on-aws-deployer --skill product-manager-co-cddo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Product Manager
Source: https://github.com/co-cddo/innovation-sandbox-on-aws-deployer/tree/main/.claude/skills/bmad/bmm/pm
Command: npx skills add https://github.com/co-cddo/innovation-sandbox-on-aws-deployer --skill product-manager-co-cddo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Crafting comprehensive Product Requirements Documents (PRDs) or technical specifications, prioritizing features, and ensuring stakeholder alignment can be a daunting task. This Skill automates the structured creation of these critical planning documents.

Core Features & Use Cases

  • PRD & Tech Spec Generation: Guides the creation of detailed Product Requirements Documents for larger projects or lightweight technical specifications for smaller ones.
  • Requirements Definition: Helps define functional, non-functional requirements, and break them into epics and user stories.
  • Feature Prioritization: Applies frameworks like MoSCoW, RICE, or Kano Model to prioritize features based on value and effort.
  • Use Case: After initial analysis, use this Skill to generate a complete PRD, defining all features, acceptance criteria, and priorities, ensuring your development team has a clear blueprint.

Quick Start

Create a Product Requirements Document for the 'MyApp' project. /prd

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 product requirements document from a brief?

A PRD converts product briefs and stakeholder inputs into structured functional and non-functional requirements, epics, user stories, and acceptance criteria. This Skill automates that conversion, ensuring requirements are testable, traceable, prioritized using frameworks like MoSCoW or RICE, and aligned to business objectives.

What's the difference between a PRD and a tech spec?

A PRD details features, user stories, and business requirements for larger projects; a tech spec is a lightweight alternative for smaller projects. This Skill generates either format based on project scope, helping teams define clear requirements without duplicating effort.

How do I prioritize features using MoSCoW, RICE, or Kano?

Feature prioritization frameworks like MoSCoW, RICE, and Kano Model rank requirements by value and effort. This Skill applies these methods to categorize features into must-haves, should-haves, and nice-to-haves, linked to business objectives for informed development planning.

Can I break requirements into epics and user stories automatically?

Yes. This Skill decomposes functional and non-functional requirements into right-sized epics and user stories with acceptance criteria, enabling development teams to work from a clear blueprint that satisfies both business and technical needs.

When should I use this during project planning?

Use this Skill in Phase 2 planning for cross-functional projects after initial analysis is complete. It resolves unclear requirements by generating comprehensive, testable, traceable specifications that prevent misalignment between product, engineering, and stakeholders.

What input do I need to generate a complete PRD?

Provide a product brief, stakeholder inputs, and project scope. This Skill converts those into a structured PRD with functional requirements, non-functional requirements, prioritized features, user stories, and acceptance criteria ready for development.