skills.rest
manhthien2005
manhthien2005COMMUNITY
Explore all skills by this author →
WebsiteGitHub

product-manager-toolkit

Prioritizes tasks with RICE and MoSCoW frameworks and plans Sprint capacity allocations.

Updated Mar 3, 2026
Search Tags:#prioritization#agile#sprint planning#backlog#capacity planning#moscow#rice scoring
One-click install
npx skills add https://github.com/manhthien2005/PM_REVIEW --skill product-manager-toolkit-manhthien2005
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: product-manager-toolkit
Source: https://github.com/manhthien2005/PM_REVIEW/tree/main/tooling/.windsurf-template/shared/skills/task-manager/skills/product-manager-toolkit
Command: npx skills add https://github.com/manhthien2005/PM_REVIEW --skill product-manager-toolkit-manhthien2005

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Product managers often struggle to objectively rank backlog items and group them into Sprints that respect team capacity and dependency constraints, leading to overloaded Sprints and misaligned priorities. ## Core Features & Use Cases - RICE Scoring: Computes a quantitative priority score from Reach, Impact, Confidence, and Effort to rank tasks objectively. - MoSCoW Classification: Categorizes requirements into Must Have, Should Have, Could Have, and Won't Have buckets mapped to Sprint ranges. - Sprint Capacity Planning: Applies velocity-based capacity formulas with a 20% buffer and grouping rules (Epic integrity, dependency ordering, BE/FE/QA balance, max 6 Epics per Sprint). - Use Case: Given a backlog of Epics with story point estimates, produce a Sprint allocation table showing which Epics land in each Sprint with total story points and rationale. ## Quick Start Use the product-manager-toolkit skill to score my backlog with RICE and group the Epics into Sprints based on a team velocity of 32 story points.

Frequently Asked Questions about product-manager-toolkit

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

FAQPage Schema
How do I prioritize a product backlog with RICE scoring?▼

RICE scoring ranks items by computing (Reach × Impact × Confidence) / Effort. Assign Impact on a 0.25x-3x scale, Confidence as 50-100%, and Effort in story points, then sort descending by score.

What is the difference between RICE and MoSCoW prioritization?▼

RICE produces a quantitative score for fine-grained ranking, while MoSCoW groups items into Must/Should/Could/Won't Have categories. Use MoSCoW for coarse release scoping and RICE when detailed ordering is needed.

How do I calculate Sprint capacity from team velocity?▼

Multiply team velocity by 0.8 to reserve a 20% buffer for unexpected work. For a 32 story point velocity, effective capacity is about 26 points, with exceptions up to 42 for infrastructure-heavy Sprints.

Can an Epic be split across multiple Sprints?▼

No, the grouping rules require all stories of one Epic to stay in the same Sprint. Dependencies must also be scheduled in earlier Sprints, and each Sprint should mix backend, frontend, and QA stories.

What are the limitations of velocity-based Sprint planning?▼

Velocity-based planning depends on accurate historical data and consistent story point estimation. It caps cognitive load at 6 Epics per Sprint but cannot account for team changes or highly uncertain exploratory work.

Related Skills

Explore More Product & Management Skills→
devsforgedevsforge
39

project-planning

Convert software ideas into structured project plans with user stories and acceptance criteria.

Official
Basic
ngochuy13ngochuy13

sprint-planner

Plan Agile sprints by selecting backlog items and calculating team capacity with buffers.

Community
Intermediate
mkolb22mkolb22

Requirement Prioritization

Prioritize backlog items using MoSCoW, RICE, and value/effort matrices.

Community
Advanced
MatrixFounderMatrixFounder
4

skill-product-backlog-prioritization

Calculate WSJF scores for product backlog items using a Python script.

Community
Intermediate