roadmap-update-skill

Gather the current roadmap state, new inputs, capacity changes, and dependency updates, then apply a scoring method such as RICE or weighted scoring to the combined backlog. Compare the new ranking against committed work and document every trade-off explicitly.

RICE ranks items quantitatively using Reach, Impact, Confidence, and Effort. MoSCoW classifies items into Must, Should, Could, and Won't for fixed time windows. Weighted scoring adds strategic dimensions like revenue impact or technical debt when RICE alone is insufficient.

Use OKR-based roadmaps when the team has mature measurable key results, quarterly frameworks when delivery cadence is predictable, Now/Next/Later for single teams with high uncertainty, and theme-based roadmaps for multi-team portfolios.

Yes, it can consume backlog items, status, and dependencies from project trackers connected via MCP, such as Jira, Productboard, or Linear. Without a connected source, you can paste data in chat or upload roadmap export files.

Build a dependency map listing each initiative's dependencies, type, status, and owner, then trace the longest chain of sequential dependencies. That chain defines the minimum timeline regardless of team capacity.

The skill never invents initiative data, RICE scores, or capacity numbers; the team must supply real data and fill in scoring frameworks. Prioritization outputs are decision inputs, not commitments, and strategic judgment remains with the team.