Use when ranking backlogs, deciding what to do first based on effort vs impact (quick wins vs big bets), prioritizing feature roadmaps, triaging bugs or technical debt, allocating resources across initiatives, identifying low-hanging fruit, evaluating strategic options with 2x2 matrix, or when user mentions prioritization, quick wins, effort-impact matrix, high-impact low-effort, big bets, or asks "what should we do first?".
SkillScore95Maintained
Automatic
◆Product Management pack
Last verified 8/24/2026
What it changes
Passed 21 of 22 test cases with the skill, and 15 of 22 without it.
Without skill68%
With skill95%
Checks it passed that the model alone missed
classifies item in the Fill-Ins quadrant
recommends executing it second after quick wins
places High Effort on the left side of the horizontal axis
and 4 more in the full report
6 fixed15 passed either way1 still failing0 broke
Pass-rate lift
+27 pp
Tokens
+187%
Agent turns
0%
Response time
-12%
Model gemini-3.6-flashMeasured 8/24/2026v121 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 6
Prompt
A developer notices a minor spelling mistake in a website footer requiring 5 minutes to fix. Classify this item on a 2x2 grid and specify when it should be completed.
What was checked, without and with the skill
Checked
Without skill
With skill
classifies item in the Fill-Ins quadrant
Missed
Passed
recommends scheduling item during downtime
Passed
Passed
case-08 · gemini-3.6-flash · 8/24/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
Transform overwhelming backlogs and option lists into clear, actionable priorities by mapping items on a 2x2 matrix of effort (cost/complexity) vs impact (value/benefit). Identify quick wins (high impact, low effort) and distinguish them from big bets (high impact, high effort), time sinks (low impact, high effort), and fill-ins (low impact, low effort).
When to Use
Use this skill when:
Backlog overflow: You have 20+ items (features, bugs, tasks, ideas) and need to decide execution order
Resource constraints: Limited time, budget, or people force trade-off decisions
Strategic planning: Choosing between initiatives, projects, or investments for quarterly/annual roadmaps
Quick wins needed: Stakeholders want visible progress fast; you need high-impact low-effort items
Trade-off clarity: Team debates "should we do A or B?" without explicit effort/impact comparison
Alignment gaps: Different stakeholders (eng, product, sales, exec) have conflicting priorities
Context switching: Too many simultaneous projects; need to focus on what matters most
New PM/leader: Taking over a backlog and need systematic prioritization approach
Common triggers:
"We have 50 feature requests, where do we start?"
"What are the quick wins?"
"Should we do the migration or the new feature first?"
"How do we prioritize technical debt vs new features?"
"What gives us the most bang for our buck?"
What Is It?
Effort-Impact Matrix (also called Impact-Effort Matrix, Quick Wins Matrix, or 2x2 Prioritization) plots each item on two dimensions:
Guide for removing skills from an existing workflow and updating all related documentation. Use when user wants to remove skills from a workflow (e.g., "remove skill", "delete skill", "移除技能", "删除技能").