Roadmap Update
AnthropicOfficialPublished by Anthropic
- Skill
- Content generator
- Business and productivity
- Apache-2.0
- No issues found
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
The roadmap-update skill provides a structured approach to managing product roadmaps. It helps users maintain alignment by integrating with project management tools or working from manual inputs to create, adjust, or reprioritize initiatives. The skill supports various frameworks like Now/Next/Later, OKR-aligned, and Quarterly Themes, while offering guidance on capacity planning, dependency management, and communicating changes to stakeholders.
What it does
- Creates new roadmaps from scratch using various strategic frameworks.
- Updates existing roadmap items, statuses, and timelines.
- Reprioritizes initiatives based on strategic shifts or new information.
- Identifies and flags risks, dependencies, and capacity constraints.
- Provides structured guidance on capacity planning and allocation.
- Generates clear summaries for different stakeholder audiences.
When to use it
- When adding new initiatives and needing to adjust existing plans to make room.
- When shifting priorities due to new strategic information or customer feedback.
- When managing timeline slips caused by dependencies or resource changes.
- When building a new roadmap view from scratch.
- When needing to communicate roadmap changes to stakeholders effectively.
Advantages
- Promotes data-driven decision making using established prioritization frameworks like RICE and ICE.
- Helps prevent over-commitment by enforcing capacity-based planning.
- Standardizes communication of roadmap changes to minimize confusion.
- Provides clear visibility into dependencies and potential risks.
- Flexible enough to support both high-level strategic views and execution-focused timelines.
Usage examples
- “Add a new initiative for 'Mobile Offline Mode' to our Q3 roadmap.”
- The agent will gather details like priority, effort, and owner, then suggest where it fits in the current roadmap and what might need to be deprioritized to accommodate it.
- “Our API integration is blocked. Update the roadmap and show the impact.”
- The agent will mark the item as blocked, analyze downstream dependencies, and provide a summary of the impact on the overall timeline.
- “Reprioritize our backlog using the RICE framework.”
- The agent will guide you through scoring your initiatives based on Reach, Impact, Confidence, and Effort to generate a ranked list.
- “Create a Now/Next/Later roadmap for our new product launch.”
- The agent will prompt for the initiatives and organize them into the Now/Next/Later format to provide a clear, strategic view of the launch plan.
Install
Download the skill as a ZIP:
https://autogineer.com/agent-skills/anthropics/roadmap-update/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip roadmap-update.zip -d .agents/skills
Documentation by Anthropic
Roadmap Update
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Update, create, or reprioritize a product roadmap.
Usage
/roadmap-update $ARGUMENTSWorkflow
1. Understand Current State
If ~~project tracker is connected:
Pull current roadmap items with their statuses, assignees, and dates
Identify items that are overdue, at risk, or recently completed
Surface any items without clear owners or dates
If no project management tool is connected:
Ask the user to describe their current roadmap or paste/upload it
Accept any format: list, table, spreadsheet, screenshot, or prose description
2. Determine the Operation
Ask what the user wants to do:
Add item: New feature, initiative, or work item to the roadmap
Gather: name, description, priority, estimated effort, target timeframe, owner, dependencies
Suggest where it fits based on current priorities and capacity
Update status: Change status of existing items
Options: not started, in progress, at risk, blocked, completed, cut
For "at risk" or "blocked": ask for the blocker and mitigation plan
Reprioritize: Change the order or priority of items
Ask what changed (new information, strategy shift, resource change, customer feedback)
Apply a prioritization framework if helpful — see Prioritization Frameworks below for RICE, MoSCoW, ICE, and value-vs-effort
Show before/after comparison
Move timeline: Shift dates for items
Ask why (scope change, dependency slip, resource constraint)
Identify downstream impacts on dependent items
Flag items that move past hard deadlines
Create new roadmap: Build a roadmap from scratch
Ask about timeframe (quarter, half, year)
Ask about format preference (Now/Next/Later, quarterly columns, OKR-aligned) — see Roadmap Frameworks below
Gather the list of initiatives to include
3. Generate Roadmap Summary
Produce a roadmap view with:
Status Overview
Quick summary: X items in progress, Y completed this period, Z at risk.
Roadmap Items
For each item, show:
Name and one-line description
Status indicator (on track / at risk / blocked / completed / not started)
Target timeframe or date
Owner
Key dependencies
Group items by:
Timeframe (Now / Next / Later) or quarter, depending on format
Or by theme/goal if the user prefers
Risks and Dependencies
Items that are blocked or at risk, with details
Cross-team dependencies and their status
Items approaching hard deadlines
Changes This Update
If this is an update to an existing roadmap, summarize what changed:
Items added, removed, or reprioritized
Timeline shifts
Status changes
4. Follow Up
After generating the roadmap:
Offer to format for a specific audience (executive summary, engineering detail, customer-facing)
Offer to draft communication about roadmap changes
If project management tool is connected, offer to update ticket statuses
Roadmap Frameworks
Now / Next / Later
The simplest and often most effective roadmap format:
Now (current sprint/month): Committed work. High confidence in scope and timeline. These are the things the team is actively building.
Next (next 1-3 months): Planned work. Good confidence in what, less confidence in exactly when. Scoped and prioritized but not yet started.
Later (3-6+ months): Directional. These are strategic bets and opportunities we intend to pursue, but scope and timing are flexible.
When to use: Most teams, most of the time. Especially good for communicating externally or to leadership because it avoids false precision on dates.
Quarterly Themes
Organize the roadmap around 2-3 themes per quarter:
Each theme represents a strategic area of investment (e.g., "Enterprise readiness", "Activation improvements", "Platform extensibility")
Under each theme, list the specific initiatives planned
Themes should map to company or team OKRs
This format makes it easy to explain WHY you are building what you are building
When to use: When you need to show strategic alignment. Good for planning meetings and executive communication.
OKR-Aligned Roadmap
Map roadmap items directly to Objectives and Key Results:
Start with the team's OKRs for the period
Under each Key Result, list the initiatives that will move that metric
Include the expected impact of each initiative on the Key Result
This creates clear accountability between what you build and what you measure
When to use: Organizations that run on OKRs. Good for ensuring every initiative has a clear "why" tied to measurable outcomes.
Timeline / Gantt View
Calendar-based view with items on a timeline:
Shows start dates, end dates, and durations
Visualizes parallelism and sequencing
Good for identifying resource conflicts
Shows dependencies between items
When to use: Execution planning with engineering. Identifying scheduling conflicts. NOT good for communicating externally (creates false precision expectations).
Prioritization Frameworks
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).
Effort: How many person-months of work? Include engineering, design, and any other functions.
When to use: When you need a quantitative, defensible prioritization. Good for comparing a large backlog of initiatives. Less good for strategic bets where impact is hard to estimate.
MoSCoW
Categorize items into Must have, Should have, Could have, Won't have:
Must have: The roadmap is a failure without these. Non-negotiable commitments.
Should have: Important and expected, but delivery is viable without them.
Could have: Desirable but clearly lower priority. Include only if capacity allows.
Won't have: Explicitly out of scope for this period. Important to list for clarity.
When to use: Scoping a release or quarter. Negotiating with stakeholders about what fits. Good for forcing prioritization conversations.
ICE Score
Simpler than RICE. Score each item 1-10 on three dimensions:
Impact: How much will this move the target metric?
Confidence: How confident are we in the impact estimate?
Ease: How easy is this to implement? (Inverse of effort — higher = easier)
ICE Score = Impact x Confidence x Ease
When to use: Quick prioritization of a feature backlog. Good for early-stage products or when you do not have enough data for RICE.
Value vs Effort Matrix
Plot initiatives on a 2x2 matrix:
High value, Low effort (Quick wins): Do these first.
High value, High effort (Big bets): Plan these carefully. Worth the investment but need proper scoping.
Low value, Low effort (Fill-ins): Do these when you have spare capacity.
Low value, High effort (Money pits): Do not do these. Remove from the backlog.
When to use: Visual prioritization in team planning sessions. Good for building shared understanding of tradeoffs.
Dependency Mapping
Identifying Dependencies
Look for dependencies across these categories:
Technical dependencies: Feature B requires infrastructure work from Feature A
Team dependencies: Feature requires work from another team (design, platform, data)
External dependencies: Waiting on a vendor, partner, or third-party integration
Knowledge dependencies: Need research or investigation results before starting
Sequential dependencies: Must ship Feature A before starting Feature B (shared code, user flow)
Managing Dependencies
List all dependencies explicitly in the roadmap
Assign an owner to each dependency (who is responsible for resolving it)
Set a "need by" date: when does the depending item need this resolved
Build buffer around dependencies — they are the highest-risk items on any roadmap
Flag dependencies that cross team boundaries early — these require coordination
Have a contingency plan: what do you do if the dependency slips?
Reducing Dependencies
Can you build a simpler version that avoids the dependency?
Can you parallelize by using an interface contract or mock?
Can you sequence differently to move the dependency earlier?
Can you absorb the work into your team to remove the cross-team coordination?
Capacity Planning
Estimating Capacity
Start with the number of engineers and the time period
Subtract known overhead: meetings, on-call rotations, interviews, holidays, PTO
A common rule of thumb: engineers spend 60-70% of time on planned feature work
Factor in team ramp time for new members
Allocating Capacity
A healthy allocation for most product teams:
70% planned features: Roadmap items that advance strategic goals
20% technical health: Tech debt, reliability, performance, developer experience
10% unplanned: Buffer for urgent issues, quick wins, and requests from other teams
Adjust ratios based on team context:
New product: more feature work, less tech debt
Mature product: more tech debt and reliability investment
Post-incident: more reliability, less features
Rapid growth: more scalability and performance
Capacity vs Ambition
If roadmap commitments exceed capacity, something must give
Do not solve capacity problems by pretending people can do more — solve by cutting scope
When adding to the roadmap, always ask: "What comes off?"
Better to commit to fewer things and deliver reliably than to overcommit and disappoint
Communicating Roadmap Changes
When the Roadmap Changes
Common triggers for roadmap changes:
New strategic priority from leadership
Customer feedback or research that changes priorities
Technical discovery that changes estimates
Dependency slip from another team
Resource change (team grows or shrinks, key person leaves)
Competitive move that requires response
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
Acknowledge impact: Who is affected and how? Stakeholders who were expecting deprioritized items need to hear it directly.
Avoiding Roadmap Whiplash
Do not change the roadmap for every piece of new information. Have a threshold for change.
Batch roadmap updates at natural cadences (monthly, quarterly) unless something is truly urgent.
Distinguish between "roadmap change" (strategic reprioritization) and "scope adjustment" (normal execution refinement).
Track how often the roadmap changes. Frequent changes may signal unclear strategy, not good responsiveness.
Output Format
Use a clear, scannable format. Tables work well for roadmap items. Use text status labels: Done, On Track, At Risk, Blocked, Not Started.
Tips
A roadmap is a communication tool, not a project plan. Keep it at the right altitude — themes and outcomes, not tasks.
When reprioritizing, always ask what changed. Priority shifts should be driven by new information, not whim.
Flag capacity issues early. If the roadmap has more work than the team can handle, say so.
Dependencies are the biggest risk to roadmaps. Surface them explicitly.
If the user asks to add something, always ask what comes off or moves. Roadmaps are zero-sum against capacity.
Files
- ATTRIBUTION.mdAdded by AutoGineer964 B
- LICENSELicence file added by AutoGineer11.1 KiB
- SKILL.md12.1 KiB
LICENSE
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
Requirements and compatibility
Written for: Claude Code, Claude apps
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Needs: Claude Code frontmatter
Security
No issues found by our static scan· No issues found
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Published by
- Anthropic
- Publisher
- Anthropic (Official)
- Source
- anthropics/knowledge-work-plugins · product-management/skills/roadmap-update · commit e050c2e
- Licence
- Apache License 2.0 (redistribution allowed)
- LICENSE (added by AutoGineer from product-management/LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by Anthropic or Anthropic.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download roadmap-update.zip