Product Manager

Generate PRDs with functional and non-functional requirements and prioritization frameworks.

472|75|Updated Oct 25, 2025

Search Tags:#planning #requirements #product management #prioritization #agile #PRD #user stories

Ready to run

npx skills add https://github.com/aj-geddes/claude-code-bmad-skills --skill product-manager

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Product Manager
Source: https://github.com/aj-geddes/claude-code-bmad-skills/tree/main/bmad-v6/skills/bmm/pm
Command: npx skills add https://github.com/aj-geddes/claude-code-bmad-skills --skill product-manager

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of comprehensive product requirements, ensuring clarity, prioritization, and alignment with user value. It prevents scope creep and ensures development focuses on testable, measurable outcomes.

Core Features & Use Cases

PRD Generation: Creates detailed Product Requirements Documents (PRDs) for complex projects.
Requirements Definition: Defines functional (FRs) and non-functional (NFRs) requirements, breaking them into epics and user stories.
Feature Prioritization: Applies frameworks like MoSCoW or RICE to prioritize features effectively.
Use Case: After a product brief, use this Skill to generate a detailed PRD, outlining all features, user stories, and acceptance criteria, ready for the architecture phase.

Quick Start

Create a Product Requirements Document (PRD) for my new 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 (PRD) for my project?▼

A PRD is a comprehensive document that defines what to build and why. This Skill generates detailed PRDs by organizing features into epics and user stories, applying prioritization frameworks like MoSCoW or RICE, and documenting functional and non-functional requirements with acceptance criteria and success metrics to align teams.

What's the best way to prioritize features when I have limited resources?▼

Feature prioritization frameworks like MoSCoW (Must, Should, Could, Won't) and RICE (Reach, Impact, Confidence, Effort) help rank features by business value and feasibility. This Skill applies these frameworks to decompose complex projects into prioritized user stories with measurable outcomes and clear implementation plans.

How do I break down an epic into user stories with clear acceptance criteria?▼

User stories translate high-level features into testable units of work. This Skill decomposes epics into granular user stories, assigns unique identifiers (FR-XXX, NFR-XXX), and defines acceptance criteria and success metrics so development teams can deliver measurable, traceable requirements.

What should a requirements document include to prevent scope creep?▼

Comprehensive requirements prevent scope creep by documenting functional and non-functional requirements with clear IDs, acceptance criteria, success metrics, and decision rationale. This Skill creates detailed PRDs and tech specs that establish a traceable baseline from backlog through delivery.

Can I use this for agile projects with evolving requirements?▼

Yes. This Skill applies agile practices by breaking work into user stories and using prioritization frameworks suited to iterative delivery. Requirements are documented with testable criteria and traceable identifiers, making them adaptable to changing priorities while maintaining clarity for cross-functional teams.

How do I ensure requirements are measurable and testable?▼

Measurable requirements include success metrics and acceptance criteria tied to observable outcomes. This Skill documents both functional requirements (what the system does) and non-functional requirements (performance, scalability), assigns unique IDs, and defines testable criteria so QA and development can validate delivery.