← Back to list
⚡

prioritize-features Checked

Prioritize a backlog of feature ideas based on impact, effort, risk, and strategic alignment with…
⚡ Productivity skills By phuryn Version v1.0.0 Added 2026-09-03 Updated 2026-09-03 Source ↗
7.5Overall rating
2Views
5Downloads
26.0kStars

Installation

🤖 Install via AI

Copy the prompt below and send it to your AI assistant (e.g. Claude Code) — it will follow the instructions and install automatically.

Install the "prioritize-features" skill by following the instructions at https://skill123.me/install/prioritize-features.
⌨️ Command line install

Run in your terminal — downloads and installs to ~/.claude/skills/.

curl -fsSL https://skill123.me/install/prioritize-features.sh | bash
📦 Download ZIP

Download the zip and extract it into your skills directory (e.g. ~/.claude/skills/), then restart your session.

⬇ Download v1.0.0 · 1 KB
📊 Static rating
7.5/10
Trigger
7.0
Structure
7.3
Workflow
6.4
Content
7.0
Engineering
8.0
Security
9.5

Six-dimension rubric with reviewer rationale.

View scorecard ↓
🛡 Dynamic test
—

Not live-tested yet — this skill is rated on static analysis only.

About this skill

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.

Documentation

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 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

Score breakdown

Trigger
7.0
Clear What/When with backlog and ranking keywords; no When-Not boundary or phrasing variants.
Structure
7.3
Single compact file; framework detail inline, references unshipped prioritization-frameworks skill.
Workflow
6.4
Task-oriented 4-step workflow with explicit criteria and ranked deliverable; no error handling or verification loop.
Content
7.0
Concise imperative steps; domain-context section is background-heavy relative to instructions.
Engineering
8.0
Frontmatter valid, no scripts, but the referenced prioritization-frameworks skill is not shipped.
Security
9.5
No scripts or injection; links to reputable productcompass.pm only.
Clear backlog-prioritization workflow with evaluation criteria and top-5 deliverable, but relies on an unshipped sibling skill and has no verification.