| name | product-roadmap |
| description | Product roadmap building: prioritisation frameworks (RICE, MoSCoW, opportunity scoring), roadmap formats, OKR alignment, stakeholder communication, and quarterly planning |
Product Roadmap Skill
When to activate
- Building or restructuring a product roadmap
- Prioritising a backlog of features and opportunities
- Aligning the roadmap to company OKRs
- Communicating roadmap to different stakeholders (engineering, sales, executives, customers)
- Running a quarterly planning process
- Deciding what to cut when capacity is constrained
When NOT to use
- Sprint-level task planning — that's delivery management, not roadmap
- Discovery (deciding what problems to solve) — use the product-discovery skill
- Writing technical specs or user stories — that's after the roadmap decision
- A/B test design — use the experiment-designer skill
Instructions
Prioritisation framework
Prioritise this backlog using [RICE / MoSCoW / opportunity scoring].
Items to prioritise: [list — can be features, projects, or problem areas]
Constraints: [team size, time horizon, budget]
Strategic goals this quarter: [OKRs or top priorities]
RICE scoring (for feature decisions):
| Item | Reach | Impact | Confidence | Effort | RICE Score |
|---|---|---|---|---|---|
| Feature A | 500 users/q | 3 (high) | 80% | 3 weeks | (500×3×0.8)/3 = 400 |
| Feature B | 1000 users/q | 1 (low) | 90% | 1 week | (1000×1×0.9)/1 = 900 |
Reach: users affected per quarter
Impact: massive=3 / high=2 / medium=1 / low=0.5 / minimal=0.25
Confidence: % certainty about reach and impact estimates
Effort: engineering weeks for one engineer
MoSCoW (for fixed-scope releases):
- Must have: without this, the release fails
- Should have: high value, include if capacity allows
- Could have: nice-to-have, first to cut
- Won't have: explicitly out of scope (prevents scope creep)
Opportunity scoring (problem-level prioritisation):
Score = Importance + (Importance − Satisfaction)
Items scoring > 10 = strong opportunity
Apply [chosen framework] to my backlog and output a prioritised list with rationale.
