Localized reading guide
roadmap-updatePurpose, usage and source
Update, create, or reprioritize your product roadmap. Use when adding a new initiative and deciding what moves to make room, shifting priorities after new information comes in, moving timelines due to a dependency slip, or building a Now/Next/Later view from scratch.
Source retrieved:
- Source repository
- anthropics/knowledge-work-plugins
- SKILL.md
product-management/skills/roadmap-update/SKILL.md- Repository stars
- 34,049
- Repository updated
- 2026-10-30
- Categories
- Business
- Last collected
License: License file needs review
Workflow excerpts are reading aids, not executable instructions from Codez. No third-party Skill was run to produce this page.
The purpose and workflow passages below are upstream material, organized and translated for reading. They are distinct from the separately labeled Codez editorial analysis.
What this Skill does
Update, create, or reprioritize your product roadmap. Use when adding a new initiative and deciding what moves to make room, shifting priorities after new information comes in, moving timelines due to a dependency slip, or building a Now/Next/Later view from scratch.
How the upstream workflow works
How to Communicate Changes
Acknowledge the change: Be direct about what is changing and why Explain the reason: What new information drove this decision? Show the tradeoff: What was deprioritized to make room? Or what is slipping? Show the new plan: Updated roadmap with the changes reflected
Upstream passage · L243 ↗Status Overview
Quick summary: X items in progress, Y completed this period, Z at risk.
Upstream passage · L63 ↗RICE Score
Score each initiative on four dimensions, then calculate RICE = (Reach x Impact x Confidence) / Effort Reach: How many users/customers will this affect in a given time period? Use concrete numbers (e.g., "500 users per quarter"). Impact: How much will this move the needle for each person reached? Score on a scale: 3 = massive, 2 = high, 1 = medium, 0.5 = low, 0.25 = minimal. Confidence: How confident are we in the reach and impact estimates? 100% = high confidence (backed by data), 80% = medium (some evidence), 50% = low (gut feel).
Upstream passage · L139 ↗/roadmap-update $ARGUMENTSRequirements and setup
Risks and Dependencies
Items that are blocked or at risk, with details Cross-team dependencies and their status
Upstream passage · L78 ↗Identifying Dependencies
Look for dependencies across these categories: Technical dependencies: Feature B requires infrastructure work from Feature A
Upstream passage · L182 ↗Limits and quality checks
No separate limits passage was selected from this file. This does not mean the Skill is safe for every input or environment. Review the complete source and validate your own result.
Start with a safe trial
- Check the supported host and the repository installation instructions. Keep the Skill directory and its referenced scripts, assets and documentation together; SKILL.md alone may omit dependencies.
- Give the agent your real input, desired output and acceptance criteria. Invocation syntax and available tools depend on the host; this site does not assume a universal install command.
- Try the source workflow in a disposable project or on a copy. Review operations that change files, remote services or billable resources before allowing them.
- Validate the output against the source quality checks and your own requirements. A successful trigger or a high repository Star count does not establish a correct result.
Read further in the source
- Roadmap Update
- 1. Understand Current State
- 2. Determine the Operation
- 3. Generate Roadmap Summary
- Status Overview
- Roadmap Items
- Risks and Dependencies
- Changes This Update
- 4. Follow Up
- Now / Next / Later
- Quarterly Themes
- OKR-Aligned Roadmap
- Timeline / Gantt View
- RICE Score
- MoSCoW
- ICE Score
- Value vs Effort Matrix
- Identifying Dependencies
- Managing Dependencies
- Reducing Dependencies
- Estimating Capacity
- Allocating Capacity
- Capacity vs Ambition
- When the Roadmap Changes
- How to Communicate Changes
- Avoiding Roadmap Whiplash
- Output Format
- Tips
Related Skills
Translation and scope
This reading guide selects passages from the pinned upstream SKILL.md. Translation is assisted. It is not a complete manual or a claim of tested compatibility. Read the original and its referenced files before use.
This introduction refers to the pinned version below; current repository activity and collection time are shown separately.
- Pinned source
- Read the original ↗
- Source retrieved
- Source commit
2574e29377c7173d0cecffef29a6ecbd7f8ccb5d- Source SHA-256
bdb121e290b590d60b94bca84d1700a8803c78db9f68f2a28fd04ccfe8aceb9e