Framework-driven approach to sequencing features and allocating resources across competing priorities.
Works with
Draws on 75 product leaders' frameworks including \"cannonballs vs. lead bullets\" (80/20 balance of big bets and incremental work), \"seasons\" for fast-changing markets, and growth models as common currency for cross-team comparison
Emphasizes separating conviction from hypothesis, challenging assumptions about impact, and using roadmaps as feasibility checks rather than commitments
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionprioritizing-roadmapExecute the skills CLI command in your project's root directory to begin installation:
Fetches prioritizing-roadmap from refoundai/lenny-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 prioritizing-roadmap. Access via /prioritizing-roadmap 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
616
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
616
stars
Help the user prioritize product roadmaps and backlogs using frameworks from 75 product leaders.
When the user asks for help with prioritization:
Alex Hardimen: "The idea of being able to take all of these crazy inputs, trying to create a very structured model to figure out, 'Okay, what is true? Where do we have conviction? Where do we have questions?'" Categorize inputs by conviction level vs. questions and rally the team around a shared context.
Asha Sharma: "We think about it as what season are we in? Season one might've been prototyping of AI and then it was all around models and reasoning models, and now it's the advent of agents." In rapidly changing environments, align the team on secular market shifts rather than rigid long-term roadmaps.
Dan Hockenmaier: "The most difficult thing about making that kind of effort is developing a common currency by which you can trade off their efforts... The growth model is the function that lets you do that." Use growth models to make projected impacts comparable across different teams during planning.
Eeke de Milliano: "At the bottom of every team charter we have a section called, Think Bigger. 'With 20% more time, what would you do that isn't on this list already?'" Explicitly ask for big ideas in planning documents to prevent teams from only focusing on incremental improvements.
Adriel Frederick: "I'm going to have some cannonballs... and I'm going to have a bunch of lead bullets. Maybe it's 80% of your energies on those big cannonballs, 20% on the lead bullets." A healthy roadmap balances high-investment "cannonballs" with incremental "lead bullets" to avoid purely incremental thinking.
Jackie Bavaro: "A roadmap in strategy is not a commitment. Instead, it's a way to double check if your plan makes any sense at all and is even anywhere near feasible." Use roadmaps to identify if you need to hire more people or take bigger swings, not as promises.
Ian McAllister: "Given the same amount of skill intelligence and resources, a product manager with a great innate ability to prioritize is going to generate 5X the impact of someone without that skill." Prioritize themes, sequence projects within those themes, and apply prioritization to personal time management.
Gibson Biddle: "These two percenters, I would kill them. If I launched something and it was only 2%... just get rid of it." Maintain product simplicity by removing features used by only a tiny fraction of users that add unnecessary complexity.
For all 91 insights from 75 guests, see references/guest-insights.md
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
I recommend prioritizing-roadmap for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Useful defaults in prioritizing-roadmap — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Solid pick for teams standardizing on skills: prioritizing-roadmap is focused, and the summary matches what you get after install.
prioritizing-roadmap is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Keeps context tight: prioritizing-roadmap is the kind of skill you can hand to a new teammate without a long onboarding doc.
Registry listing for prioritizing-roadmap matched our evaluation — installs cleanly and behaves as described in the markdown.
Useful defaults in prioritizing-roadmap — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
prioritizing-roadmap fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
prioritizing-roadmap has been reliable in day-to-day use. Documentation quality is above average for community skills.
prioritizing-roadmap fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 49