product-manager

Create PRDs with RICE scoring, user stories, and metrics.

4|1|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/xcrrr/claude-skills --skill product-manager-xcrrr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: product-manager
Source: https://github.com/xcrrr/claude-skills/tree/main/skills/business/product-manager
Command: npx skills add https://github.com/xcrrr/claude-skills --skill product-manager-xcrrr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Product teams often struggle to align on requirements, priorities, and success metrics across features and roadmaps. This skill provides repeatable PRD templates, prioritization frameworks (RICE, MoSCoW), and clear user stories with acceptance criteria to accelerate decision-making and handoffs.

Core Features & Use Cases

  • PRD templates covering Overview, Problem, Goals, Users, Requirements, Metrics, Risks, Timeline.
  • Prioritization and planning: RICE scoring, MoSCoW method, OKR-aligned roadmaps.
  • User story and acceptance criteria templates: "As a user, I want..." and Given/When/Then scenarios.
  • Metrics definition: North Star metric, secondary metrics, and guardrails for feature health.

Quick Start

Provide a one-page brief including feature name, objective, users, problems, success metrics, and a prioritized backlog using RICE.

Frequently Asked Questions about product-manager

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

FAQPage Schema
How do I write a PRD that covers problem, goals, and metrics all in one document?

To write a comprehensive PRD, structure your document with dedicated sections for Overview, Problem, Goals, Users, Requirements, Metrics, Risks, and Timeline. This ensures complete product planning coverage and aligns teams on requirements and success criteria.

What is the best way to prioritize features using RICE and MoSCoW methods?

Prioritize features by applying RICE scoring to quantify Reach, Impact, Confidence, and Effort, then use the MoSCoW method to categorize items as Must, Should, Could, or Won't have. This combination accelerates data-driven decision-making for product roadmaps.

How do I draft user stories with acceptance criteria for engineering handoffs?

Draft user stories using the "As a user, I want..." format, then attach acceptance criteria structured as Given/When/Then scenarios. This provides clear, testable conditions for development teams and streamlines feature handoffs.

What product metrics should I define for feature health and roadmaps?

Define product metrics by establishing a North Star metric for primary goals, secondary metrics for supporting insights, and guardrail metrics to prevent negative outcomes. This framework tracks feature health and aligns with OKR-based roadmaps.

Do I need a prioritized backlog to start defining product metrics and roadmaps?

You need a one-page brief with a feature name, objective, users, problems, and success metrics to start. Providing a prioritized backlog using RICE alongside this brief allows accurate roadmap planning and metrics definition.