Skip to content
SkillModel-led481 tokens in use

prioritize-features

Score a feature backlog on impact, effort, risk and strategic fit, and get a ranked top five with the trade-offs spelled out.

28,201 stars on the repository MIT Licensephuryn/pm-skills · pm-product-discovery/skills/prioritize-features
claude plugin install pm-product-discovery@pm-skills
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing prioritize-features costs

46tokens idle
481tokens in use

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

Nothing detected: no shell, network, file writes, git or credentials in its files.

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Good
  • Frontmatter12/15
  • Structure22/25
  • Examples0/15
  • Output10/15
  • Size15/15
  • Resources10/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent

No findings.

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Good
  • Development activity80
  • Maintenance76
  • Community60
  • Maturity32
  • Momentum40

This skill evaluates a backlog of feature ideas against the product objective. Each feature is judged on impact, effort, risk and strategic alignment, using Opportunity Score when customer data is available, with ICE and RICE as scoring options.

It returns the five features to pursue, with a rationale for each, the trade-offs considered and what was deprioritized and why. A prioritization table is added when it helps.

What You Get

  • A ranked top five with a short rationale for each pick
  • The trade-offs that shaped the ranking
  • A list of deprioritized features with reasons
  • An optional prioritization table, saved as markdown when large

Common Use Cases

  • Narrowing a long feature backlog before a planning cycle
  • Making scope decisions with a clear rationale to share
  • Ranking ideas from a spreadsheet of customer requests

What Makes It Unique

It prioritizes problems before solutions, using Opportunity Score from The Lean Product Playbook, and it asks for deprioritization reasons as well as a winners list. For picking a framework it points to the prioritization-frameworks skill.

Under The Hood

The skill is a prompt only, with no scripts. It tells the agent to read and analyze any spreadsheets, backlogs or assessments the user provides, and to save substantial output as markdown. It refers to the prioritization-frameworks skill for formulas. It makes no web or API calls.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers