Prioritize a backlog of feature ideas based on impact, effort, risk, and strategic alignment with top 5 recommendations. Use when prioritizing a feature backlog, making scope decisions, or ranking product ideas.
prioritize-features evaluates and ranks a backlog of feature ideas to identify the top 5 to pursue, scoring them on impact, effort, risk, and strategic alignment. It solves the recurring product management problem of deciding what to build next when there are more ideas than capacity, and applies when prioritizing a feature backlog, making scope decisions, or ranking product ideas. If the user provides files such as spreadsheets, backlogs, or opportunity assessments, the skill reads and analyzes them directly.
The skill grounds its scoring in established prioritization frameworks and points to a companion prioritization-frameworks skill for framework selection. It recommends the Opportunity Score from Dan Olsen's The Lean Product Playbook for evaluating customer problems, defined as Importance x (1 - Satisfaction) normalized to 0-1, where high importance and low satisfaction indicate the best opportunities, and it stresses prioritizing problems (opportunities) rather than solutions. For quick scoring of initiatives it recommends ICE (Impact x Confidence x Ease, where Impact can be Opportunity Score x number of customers), with RICE adding Reach as a separate factor for larger teams. The instructions walk through confirming the product objective and success metrics, evaluating each feature against impact, effort, risk, and strategic alignment, and then recommending the top 5 with clear ranking, brief rationale, key trade-offs, and what was deprioritized and why, optionally presented as a prioritization table.
Target users are product managers and teams making roadmap and scope decisions. The skill takes the product objective, desired outcomes, and feature ideas as input (via $ARGUMENTS) and produces a ranked shortlist with reasoning; it suggests saving the output as markdown if substantial. It also links further reading on the Kano Model and product management framework compendiums. Its guidance is advisory and depends on the quality of inputs, including any customer importance and satisfaction data available for computing Opportunity Scores.
Each feature is evaluated against impact (how much it moves desired outcomes, optionally using Opportunity Score), effort (development, design, and coordination required), risk (uncertainty and assumptions to test), and strategic alignment with the product vision and current goals.
Opportunity Score (Importance x (1 - Satisfaction), normalized 0-1) from Dan Olsen's The Lean Product Playbook for evaluating customer problems, ICE (Impact x Confidence x Ease) for quick initiative scoring, and RICE (adding Reach) for larger teams. For deeper framework selection it points to the prioritization-frameworks skill.
It recommends the top 5 features with a clear 1-5 ranking, brief rationale for each, key trade-offs considered, and what was deprioritized and why, optionally presented as a prioritization table. It suggests saving as markdown if the output is substantial.
Yes. If the user provides files such as spreadsheets, backlogs, or opportunity assessments, the skill reads and analyzes them directly.
The skill emphasizes prioritizing problems (opportunities), not solutions, using the Opportunity Score approach where high importance combined with low satisfaction identifies the best opportunities.
Quick Setup:
.claude/skills/Repository
phuryn/pm-skills