โ† ClaudeAtlas

roadmap-migratelisted

{{ ๐›€๐›€๐›€ }} Convert an old simple-style roadmap (single Markdown, four statuses, <a name> anchors, roadmaps.json pointer registry) into the rich phase-array format (roadmaps.json source of truth + PHASE task list + prose overview).
JasonWarrenUK/goblin-mode ยท โ˜… 5 ยท Data & Documents ยท score 73
Install: claude install-skill JasonWarrenUK/goblin-mode
Upgrade an old **simple-format** roadmap to the **rich phase-array format** the other `roadmap-*` skills expect. This is a one-way structural rewrite of the source of truth, so it is user-initiated only (never model-triggered) โ€” the other skills detect the old format and point the user here. **Old (simple) format:** a single `docs/roadmaps/{name}.md` is the source of truth, with `<a name="m{N}">` anchors, four sections (In Progress / To Do / Blocked / Completed), `- [ ]`/`- [x]` checkboxes, prose `โ€” **depends on {IDs}**`, a `graph TD` diagram; `.claude/roadmaps.json` is a `{"roadmaps":[{name,path}]}` pointer registry. **Rich format:** `.claude/roadmaps.json` is the source of truth โ€” an **array of phase objects** `{name, path, archived?, externalGates, milestones}` with six statuses (`todo, blocked, paused, deferred, done, out_of_scope`), external gates, milestone/gate dependencies, and a mechanical status recompute. `docs/roadmaps/{PHASE}.md` and `docs/reports/ROADMAP_OVERVIEW.md` are projections. Shared conventions: `~/.claude/library/references/roadmap-conventions.md`. The CLI is `python3 "$HOME"/.claude/library/scripts/roadmap.py`. ## Steps ### 1. Locate and confirm it is old format Resolve the roadmap: `$ARGUMENTS` path/name โ†’ `.claude/roadmaps.json` โ†’ `docs/roadmaps/` scan. Run `python3 "$HOME"/.claude/library/scripts/roadmap.py detect`: - Exit **3** โ€” old format, proceed. - Exit **0** โ€” already rich; tell the user there is nothing to migrate and stop. - Exit **2*