Repeatable post-release beat — celebrate the shipped release, then plan the next roadmap as cornerstones + rationale (NOT an exhaustive list) + an explicit deferred set, scoped into a GitHub milestone with a named steward per epic. Triggers: a release ships (vX.Y merged to main); a maintainer says "scope the next release / plan the roadmap / what's in vNext"; or the post-release planning beat is neglected. Sibling to #10321 (release-cut: notes + publish).
Installs into .claude/skills of the current project.
Are you the author of Update Roadmap?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/neomjs-update-roadmap)
---
name: update-roadmap
description: Repeatable post-release beat — celebrate the shipped release, then plan the next roadmap as cornerstones + rationale (NOT an exhaustive list) + an explicit deferred set, scoped into a GitHub milestone with a named steward per epic. Triggers: a release ships (vX.Y merged to main); a maintainer says "scope the next release / plan the roadmap / what's in vNext"; or the post-release planning beat is neglected. Sibling to #10321 (release-cut: notes + publish).
---
# Update Roadmap
If you are running the post-release planning beat — celebrating a shipped release and scoping the next one (its milestone's cornerstones, rationale, deferred set, and epic stewards) — you MUST immediately use the `view_file` tool to read and strictly adhere to `.agents/skills/update-roadmap/references/update-roadmap-workflow.md` before drafting any roadmap, milestone, or scope artifact.
