AutoGineer
Generated banner for Prioritize Features
Generated logo for Prioritize Features

Prioritize Features

Pawel HurynCommunityCreated by Pawel Huryn

  • Skill
  • Research and analysis
  • Business and productivity
  • MIT
  • No issues found
Download ZIP

From the author

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.
— the description by Pawel Huryn

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

The prioritize-features skill provides a systematic approach to backlog management. It guides users through evaluating feature ideas against key business metrics, including impact, effort, risk, and strategic alignment. By leveraging established methodologies like Opportunity Scoring and RICE, the skill helps product teams move from a list of ideas to a ranked set of the top 5 recommendations, ensuring that development efforts are focused on the most valuable opportunities.

What it does

  • Analyzes feature backlogs and product opportunity assessments.
  • Evaluates features based on impact, effort, risk, and strategic alignment.
  • Applies prioritization frameworks like Opportunity Score and RICE.
  • Generates a ranked list of the top 5 recommended features.
  • Provides rationales and trade-off analysis for prioritization decisions.
  • Identifies features to deprioritize and explains the reasoning.

When to use it

  • When you need to rank a long list of feature ideas for a product roadmap.
  • When making difficult scope decisions during product planning.
  • When you need to justify feature selection to stakeholders using data-backed criteria.
  • When transitioning from a broad list of ideas to a focused development plan.

Advantages

  • Reduces subjectivity in product decision-making.
  • Ensures alignment between product features and strategic goals.
  • Provides a clear, defensible rationale for the chosen roadmap.
  • Helps teams identify and mitigate risks early in the planning process.

Usage examples

“Here is my feature backlog for our mobile app. Please prioritize these based on impact and effort.”
The agent will analyze the provided list, apply the RICE or Opportunity Score framework, and return a table ranking the top 5 features with justifications.
“We need to decide which features to build next quarter. Our goal is user retention. Here are our ideas.”
The agent will evaluate the ideas specifically against the goal of user retention, considering risk and strategic alignment to recommend the best path forward.

Install

  1. Download the skill as a ZIP:

    https://autogineer.com/agent-skills/phuryn/prioritize-features/download

  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip prioritize-features.zip -d .agents/skills

Documentation by Pawel Huryn

Prioritize Feature Backlog

Evaluate and rank a backlog of feature ideas to identify the top 5 to pursue.

Context

You are helping prioritize features for $ARGUMENTS.

If the user provides files (spreadsheets, backlogs, opportunity assessments), read and analyze them directly.

Domain Context

For framework selection guidance, see the prioritization-frameworks skill. Key recommendations:

Opportunity Score (Dan Olsen, The Lean Product Playbook) is recommended for evaluating customer problems: Opportunity Score = Importance × (1 − Satisfaction), normalized to 0–1. High Importance + low Satisfaction = best opportunities. Prioritize problems (opportunities), not solutions.

ICE is recommended for quick scoring of initiatives: Impact (Opportunity Score × # Customers) × Confidence × Ease. RICE adds Reach as a separate factor for larger teams.

Instructions

The user will describe their product objective, desired outcomes, and provide feature ideas. Work through these steps:

  1. Understand priorities: Confirm the product objective and success metrics.

  2. Evaluate each feature against:

    • Impact: How much does it move the needle on desired outcomes? Consider Opportunity Score if customer data is available.

    • Effort: How much development, design, and coordination is required?

    • Risk: How much uncertainty exists? What assumptions need testing?

    • Strategic alignment: How well does it fit the product vision and current goals?

  3. Recommend the top 5 features with:

    • Clear ranking (1-5)

    • Brief rationale for each selection

    • Key trade-offs considered

    • What was deprioritized and why

  4. Present as a prioritization table if helpful.

Think step by step. Save as markdown if the output is substantial.

Further Reading

Files

SKILL.md

Prioritize Feature Backlog

Evaluate and rank a backlog of feature ideas to identify the top 5 to pursue.

Context

You are helping prioritize features for $ARGUMENTS.

If the user provides files (spreadsheets, backlogs, opportunity assessments), read and analyze them directly.

Domain Context

For framework selection guidance, see the prioritization-frameworks skill. Key recommendations:

Opportunity Score (Dan Olsen, The Lean Product Playbook) is recommended for evaluating customer problems: Opportunity Score = Importance × (1 − Satisfaction), normalized to 0–1. High Importance + low Satisfaction = best opportunities. Prioritize problems (opportunities), not solutions.

ICE is recommended for quick scoring of initiatives: Impact (Opportunity Score × # Customers) × Confidence × Ease. RICE adds Reach as a separate factor for larger teams.

Instructions

The user will describe their product objective, desired outcomes, and provide feature ideas. Work through these steps:

  1. Understand priorities: Confirm the product objective and success metrics.

  2. Evaluate each feature against:

    • Impact: How much does it move the needle on desired outcomes? Consider Opportunity Score if customer data is available.

    • Effort: How much development, design, and coordination is required?

    • Risk: How much uncertainty exists? What assumptions need testing?

    • Strategic alignment: How well does it fit the product vision and current goals?

  3. Recommend the top 5 features with:

    • Clear ranking (1-5)

    • Brief rationale for each selection

    • Key trade-offs considered

    • What was deprioritized and why

  4. Present as a prioritization table if helpful.

Think step by step. Save as markdown if the output is substantial.

Further Reading

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
Pawel Huryn
Publisher
Pawel Huryn (Community)
Source
phuryn/pm-skills · pm-product-discovery/skills/prioritize-features · commit 2a12295
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Pawel Huryn or Pawel Huryn.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download prioritize-features.zip