Merge research-grounded technical program management skill with routing, templates, evals, and repository validation.
Product Roadmapping and Portfolio Management
Build roadmaps that communicate strategic intent — not project schedules.
Why Install This Skill
Most roadmap tools produce feature lists with dates, creating two problems: stakeholders treat every date as a promise, and the roadmap becomes a project schedule. When a dependency invalidates a date, the document loses credibility. This skill replaces date-first roadmapping with outcome-based sequencing: Now/Next/Later views, strategic-bet management, explicit continue/pause/kill/revisit criteria, and scenario planning.
What You Get
| Directory | Content |
|---|---|
SKILL.md |
Core methodology, loading guide, routing table |
references/discovery-brief.md |
Where RICE/Kano/OST/MoSCoW live, ownership boundaries |
references/outcome-roadmapping.md |
Now/Next/Later roadmaps with capacity constraints |
references/strategic-bets.md |
Bet records: confidence, risk, dependencies, criteria |
references/dependency-confidence-view.md |
Cross-bet dependency mapping and confidence calibration |
references/scenario-comparison.md |
Alternative-future scenario planning |
references/roadmap-review-cadence.md |
Review processes and stakeholder communication |
templates/outcome-roadmap.md |
Fillable roadmap template |
templates/bet-record.md |
Fillable bet record template |
templates/roadmap-review-record.md |
Fillable review record template |
evals/evals.json |
5 eval cases covering mandatory scenarios |
Quick Start
Load the skill. For roadmaps: references/outcome-roadmapping.md. For bets: references/strategic-bets.md. For portfolio risk: references/dependency-confidence-view.md. For reviews: references/roadmap-review-cadence.md.
Triggers
Load when: building/reviewing product roadmaps, managing strategic bets, defining continue/pause/kill/revisit criteria, mapping dependencies and confidence, comparing scenarios, designing roadmap reviews, communicating roadmap decisions.
Do NOT load for: tactical prioritization (use product-methodology or product-strategy), project scheduling, delivery-flow management (use kanban-guru), capital allocation (use strategy-frameworks).
Requirements
No API keys, dependencies, or system tools required.