prioritize-features

Rank candidate features by demand evidence, strategic fit, and initiative status.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/tylersahagun/elmer --skill prioritize-features-tylersahagun
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prioritize-features
Source: https://github.com/tylersahagun/elmer/tree/main/.cursor/skills/prioritize-features
Command: npx skills add https://github.com/tylersahagun/elmer --skill prioritize-features-tylersahagun

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps product teams objectively rank potential features by considering their potential demand, alignment with company strategy, and current initiative status, preventing resources from being wasted on low-impact or misaligned work.

Core Features & Use Cases

  • Evidence-Based Prioritization: Ranks features using provided signals (e.g., user feedback, market research).
  • Strategic Alignment: Assesses how well each feature fits into the broader company objectives and existing initiatives.
  • Use Case: A product manager can input a list of new feature ideas along with user feedback data and current roadmap priorities. The Skill will then output a ranked list of features, clearly indicating which ones offer the most strategic value and should be considered next.

Quick Start

Use the prioritize-features skill to rank the new feature ideas based on the latest user signals and our current strategic roadmap.

Frequently Asked Questions about prioritize-features

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prioritize features based on user feedback and roadmap strategy?

Feature prioritization evaluates candidate features by scoring demand evidence from user signals, strategic fit, and current initiative status to generate a ranked list. This prevents wasting resources on low-impact or misaligned product work.

What is the best way to rank feature opportunities for product discovery?

Ranking feature opportunities for product discovery involves ordering candidate features by their potential demand and alignment with company objectives. It requires input artifacts like user signals and roadmap context to accurately score and route features into strategic initiatives.

How do I align new feature ideas with existing strategic initiatives?

Aligning new feature ideas with strategic initiatives requires assessing how well each candidate fits into the broader company objectives and current initiative status. This ensures selected features directly support existing roadmap priorities and prevent misaligned work.

What inputs do I need to rank features by value and strategy?

Ranking features by value and strategy requires input artifacts including user signals for demand evidence, initiative-status context, and current roadmap data. Accurate scoring depends on providing these specific product discovery inputs to evaluate strategic fit.

When should I use evidence-based feature ranking instead of subjective selection?

Evidence-based feature ranking should be used when you need to objectively order potential features using market research and user feedback. It prevents subjective bias by evaluating demand evidence and strategic alignment to efficiently route high-impact opportunities into your roadmap.

Can I rank features if my current roadmap context is incomplete?

Ranking features with incomplete roadmap context is not recommended because accurate scoring depends on initiative-status and strategic alignment data. Missing these input artifacts reduces the reliability of the feature ranking and may lead to misaligned product discovery outcomes.