roadmap-createlisted

Create a roadmap as three synchronised artefacts: - `.claude/roadmaps.json` — machine-readable **source of truth**, an **array of phase objects** each `{name, path, archived?, externalGates, milestones}`. The active phase is the entry without `archived: true`; archived entries are retained as historical record. - `docs/roadmaps/{PHASE}.md` — human-readable task list and dependency diagram (a projection). - `docs/reports/ROADMAP_OVERVIEW.md` — prose overview (a projection). When creating a new phase alongside existing ones, append a new element and mark the superseded phase `"archived": true`. Shared conventions (status vocabulary, colour table, graph rules, formatting) live in `~/.claude/library/references/roadmap-conventions.md` — read it before writing anything. The CLI is `python3 "$HOME"/.claude/library/scripts/roadmap.py`. ## Behaviour | Codebase Context | Arguments Passed | Action | | ----------------- | ---------------- | --------------------------------------------------------- | | No other roadmaps | 0 | Create the first project roadmap (default `PHASE_1.md`) | | N/A | 1 | Create the roadmap/phase named in the argument | | Roadmaps exist | 0 | Ask the user which phase to create or if starting a new phase | ## Steps ### 1. Determine scope, context, and format - Check if `docs/roadmaps/` exists and contains roadmaps; check if `.claude/r