Evaluate and rank a backlog of feature ideas to identify the top 5 to pursue.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionprioritize-featuresExecute the skills CLI command in your project's root directory to begin installation:
Fetches prioritize-features from phuryn/pm-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate prioritize-features. Access via /prioritize-features in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
9.6K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
9.6K
stars
Evaluate and rank a backlog of feature ideas to identify the top 5 to pursue.
You are helping prioritize features for $ARGUMENTS.
If the user provides files (spreadsheets, backlogs, opportunity assessments), read and analyze them directly.
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.
The user will describe their product objective, desired outcomes, and provide feature ideas. Work through these steps:
Understand priorities: Confirm the product objective and success metrics.
Evaluate each feature against:
Recommend the top 5 features with:
Present as a prioritization table if helpful.
Think step by step. Save as markdown if the output is substantial.
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
Useful defaults in prioritize-features — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
prioritize-features fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
prioritize-features is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
I recommend prioritize-features for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
prioritize-features has been reliable in day-to-day use. Documentation quality is above average for community skills.
Keeps context tight: prioritize-features is the kind of skill you can hand to a new teammate without a long onboarding doc.
prioritize-features is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
prioritize-features has been reliable in day-to-day use. Documentation quality is above average for community skills.
prioritize-features reduced setup friction for our internal harness; good balance of opinion and flexibility.
I recommend prioritize-features for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 68