prioritizing-roadmap

Prioritize product roadmaps and backlogs using frameworks from 75 product leaders.

1|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/AlexYedi/Empire_State_Events_Pipeline_Take_3 --skill prioritizing-roadmap-alexyedi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prioritizing-roadmap
Source: https://github.com/AlexYedi/Empire_State_Events_Pipeline_Take_3/tree/main/.claude/skills/prioritizing-roadmap
Command: npx skills add https://github.com/AlexYedi/Empire_State_Events_Pipeline_Take_3 --skill prioritizing-roadmap-alexyedi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Product teams struggle to decide what to build next when facing competing stakeholder requests, limited resources, and too many candidate features. This Skill provides structured prioritization guidance drawn from 91 insights across 75 product leaders. ## Core Features & Use Cases - Prioritization Frameworks: Apply proven approaches like ICE scoring, the 4 BB model, 70/20/10 portfolio allocation, Now-Next-Later roadmaps, and cannonballs vs lead bullets balancing. - Leverage-Point Distribution Check: Score roadmap candidates against systems-thinking leverage points to ensure at least some work targets strategic layers rather than only low-leverage fixes. - Mistake Detection: Flag common anti-patterns such as prioritizing by loudest voice, all-incremental roadmaps, and never removing low-usage features. - Use Case: A PM preparing quarterly planning can use this Skill to pressure-test their roadmap, balance big bets against incremental work, and build a narrative instead of a feature spreadsheet. ## Quick Start Help me prioritize my product roadmap for next quarter given these candidate features and our team capacity.

Frequently Asked Questions about prioritizing-roadmap

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

FAQPage Schema
How do I prioritize a product roadmap with too many competing requests?

Start by separating truth from hypothesis: categorize inputs by conviction level versus open questions. Then apply a framework like ICE scoring or the 4 BB model to compare candidates, and balance big bets against incremental lead bullets using an explicit allocation like 80/20.

What prioritization frameworks does this skill cover?

It covers ICE scoring, the 4 BB framework (Brilliant Basics, Bread and Butter, Big Bets, Breaking Bad), 70/20/10 portfolio allocation, Now-Next-Later roadmaps, outcome roadmaps, and a leverage-point distribution check from systems thinking.

How do I balance big bets versus incremental improvements on a roadmap?

Use an explicit resource split such as 80% of effort on high-investment cannonballs and 20% on incremental lead bullets. Early-stage products should weight almost entirely toward big bets, while mature products can follow a 70/20/10 core-strategic-bets model.

When should I remove features instead of adding new ones?

Remove features used by only a tiny fraction of users, often called two percenters, because they add maintenance complexity without broad value. Regularly measure feature reach and scrape the barnacles to keep the product simple.

What are common roadmap prioritization mistakes to avoid?

Common mistakes include prioritizing by the loudest stakeholder voice, filling the roadmap with only safe incremental work, treating roadmaps as feature spreadsheets without narrative, never saying no, and optimizing only for quick ROI wins.