Feature Prioritization Assistant
- 463 installs
- 43 repo stars
- Updated March 7, 2026
- pmprompt/claude-plugin-product-management
feature-prioritization-assistant is an agent skill that calculates RICE scores and ranks backlog features by impact, effort, and strategic fit for developers and PMs planning sprint, roadmap, or MVP scope.
About
feature-prioritization-assistant is a product management agent skill from pmprompt/claude-plugin-product-management that applies the RICE framework to prioritize features systematically. Given product context, optional research data, and a list of candidate features, the skill scores reach, impact, confidence, and effort then ranks items for data-driven roadmap, sprint, or MVP cut-line decisions on SaaS and platform products. Developers and PMs reach for feature-prioritization-assistant when building a product roadmap and need consistent prioritization instead of subjective stack ranking. The skill accepts an argument hint for features to evaluate and combines industry PM best practices for practical day-to-day backlog triage. It suits quarterly planning sessions, sprint commitment meetings, and MVP scope reduction when tradeoffs must be explicit and comparable across initiatives.
- Impact-effort framing for backlog items
- Roadmap and sprint cut-line guidance
- Strategic-fit checks against goals
- Tradeoff narratives for stakeholders
- Repeatable prioritization workflow
Feature Prioritization Assistant by the numbers
- 463 all-time installs (skills.sh)
- +20 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Ranked #778 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
- Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/pmprompt/claude-plugin-product-management --skill feature-prioritization-assistantAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 463 |
|---|---|
| repo stars | ★ 43 |
| Last updated | March 7, 2026 |
| Repository | pmprompt/claude-plugin-product-management ↗ |
How do you prioritize SaaS features with RICE?
Rank backlog items using impact, effort, and strategic fit when planning the next sprint, quarter roadmap, or MVP cut line for a SaaS or platform product.
Who is it for?
Product managers and tech leads planning SaaS roadmaps who want systematic RICE prioritization across a defined feature list.
Skip if: Engineering implementation tasks or teams without a feature backlog to score and compare.
When should I use this skill?
User asks to prioritize features, score a backlog with RICE, or decide MVP scope for an upcoming sprint or quarter.
What you get
RICE-scored feature ranking, prioritized backlog table, and roadmap or sprint recommendations with explicit tradeoffs.
- RICE score table
- prioritized backlog ranking
- roadmap recommendations
Files
Domain Context
This skill implements a proven product management framework. The approach combines best practices from industry leaders and is designed for practical application in day-to-day PM work.
Input Requirements
- Context about your product, feature, or problem
- Relevant data, research, or constraints (recommended but optional)
- Clear articulation of what you're trying to achieve
Feature Prioritization Assistant
When to Use
- Building your product roadmap
- Need to choose between multiple feature ideas
- Stakeholders are debating which features to build first
- Want to make data-driven prioritization decisions
- Need to justify prioritization decisions to leadership
What This Skill Does
Helps you systematically evaluate and prioritize features using the RICE framework (Reach, Impact, Confidence, Effort), providing scores and recommendations.
Instructions
Help me prioritize these features using the RICE framework. For each feature, help me estimate:
1. Reach: How many users will this impact per month? 2. Impact: How much will this impact each user? (Scale: 0.25=minimal, 0.5=low, 1=medium, 2=high, 3=massive) 3. Confidence: How confident are we in our estimates? (Scale: 0-100%) 4. Effort: How many person-months will this take to build?
Then calculate the RICE score: (Reach × Impact × Confidence) / Effort
Features to evaluate: [List your features with any context you have]
Best Practices
- Gather data on current user behavior before estimating Reach
- Base Impact on user research and pain point severity
- Be honest about Confidence levels - lower confidence for assumptions
- Include design, development, and testing time in Effort estimates
- Revisit estimates after initial discovery work
- Consider dependencies between features
Example
Input: 5 features (notifications, dark mode, API access, mobile app, analytics dashboard) Output: RICE scores calculated for each, ranked list with reasoning, recommendations on which to prioritize, and suggestions for validating assumptions on low-c...
Related skills
Grill MeHave an agent relentlessly pressure-test their plan or design until every decision branch is resolved and shared understanding is reached.691k196kGrill With DocsPressure-test architecture decisions against their live codebase and living documentation before writing production code.585k196k
Lark CalendarLet their coding agents read, create, and manage events inside Lark (Feishu) Calendar directly from natural language instructions.493kLark ImLet their coding agent send instant notifications, post updates, and receive commands directly inside Lark (Feishu) workspaces.493kLark ContactLet their AI coding agents read and write contacts, send messages, and manage user data inside Lark (Feishu).493kLark AttendanceAutomatically fetch and report daily attendance data from Lark (Feishu) into their own tools or agents.493kHow it compares
Pick feature-prioritization-assistant for scored backlog ranking; use PRD or discovery skills when the problem is undefined features rather than ordering known ones.
FAQ
What framework does feature-prioritization-assistant use?
feature-prioritization-assistant uses the RICE framework, scoring Reach, Impact, Confidence, and Effort for each feature. The skill ranks backlog items systematically to support sprint, roadmap, and MVP prioritization decisions on SaaS products.
What input does feature-prioritization-assistant need?
feature-prioritization-assistant needs product context, a clear goal, and the features to evaluate via argument hint. Optional research or constraints improve scoring accuracy when planning roadmap or sprint commitments.