roadmap-update

Describe what changed, such as new strategy, customer feedback, or a resource shift, and the Skill applies a prioritization framework like RICE or MoSCoW to reorder items. It shows a before-and-after comparison and summarizes what moved and why.

Use RICE for quantitative comparison of a large backlog, ICE for quick scoring with limited data, MoSCoW for scoping a release with stakeholders, and value-vs-effort for visual team planning sessions. The Skill explains when each fits.

Provide your list of initiatives and preferred timeframe, and the Skill groups items into Now (committed work), Next (planned, 1-3 months), and Later (directional, 3-6+ months). This format avoids false precision on dates when communicating externally.

Yes. If no project tracker is connected, you can paste or describe your current roadmap in any format including lists, tables, spreadsheets, or prose, and the Skill works from that input directly.

The Skill identifies downstream impacts of a slipped dependency, flags items approaching hard deadlines, and suggests mitigations such as building against an interface contract, resequencing work, or adding buffer around cross-team dependencies.

Avoid changing the roadmap for every new piece of information. Batch updates at monthly or quarterly cadences, distinguish strategic reprioritization from normal scope adjustment, and track change frequency since constant churn signals unclear strategy.