agentleFS
Sign inStart free
AdhamxonAdhamxon/claude-code-skills/.claude/skills/prioritize-features/SKILL.md

prioritize-features

Skill2 starsChanged 3 months agoMITView on GitHub

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.

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

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

    line 14
  2. Distinctive:

    Present as a prioritization table: if helpful.

    line 42

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free