Menu
{{ 𝚫𝚫𝚫 }} Generate the HTML roadmap dashboard deterministically via roadmap.py render.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
{{ 𝚫𝚫𝚫 }} Rebuild roadmap-system.zip, the distributable snapshot of the roadmap tooling (scripts, HTML template, conventions reference, and every roadmap-touching skill, including this one).
{{ 𝛀𝛀𝛀 }} Create a project roadmap in the rich phase-array format — roadmaps.json as source of truth plus a PHASE task list and prose overview
{{ 𝛀𝛀𝛀 }} Recompute and synchronise roadmap task statuses across roadmaps.json and its projections, with optional codebase reconciliation
{{ 𝛀𝛀𝛀 }} Add a task to a rich-format project roadmap with correct ID, dependency wiring, and graph integrity — ID assignment, status computation, dependency edges in both directions, and no unconnected islands.
Git workflow: branch management, commit conventions, PR patterns, conflict resolution.
{{ 𝛀𝛀𝛀 }} Review a pull request and post it as a GitHub review
| name | Artefacts: Create Roadmap |
| description | {{ 𝚫𝚫𝚫 }} Generate the HTML roadmap dashboard deterministically via roadmap.py render. |
| when_to_use | When you want to view or share the current roadmap as an interactive dashboard rather than reading roadmaps.json directly. |
| model | haiku |
| disable-model-invocation | true |
| allowed-tools | ["Read","Glob","Bash(python3:*)","Bash(open:*)"] |
| argument-hint | ["phase name (optional","when several are active)"] |
Render the interactive roadmap dashboard. The HTML is generated deterministically by roadmap.py render from the template at ~/.claude/library/templates/roadmap-artefact.html — this skill runs the command and opens the result; it writes no HTML itself. Same data in, same file out, so regenerated artefacts diff cleanly and can never drift from roadmaps.json.
Shared conventions (statuses, colour table): ~/.claude/library/references/roadmap-conventions.md.
python3 "$HOME"/.claude/library/scripts/roadmap.py detect. Exit 3 = old simple format — stop and tell the user to run roadmap-migrate first. Exit 2 = could not locate/parse — ask for the path. Proceed on exit 0.python3 "$HOME"/.claude/library/scripts/roadmap.py render, adding --phase "$ARGUMENTS" when the user named a phase (required if several are active). Default output: {project_root}/docs/artefacts/roadmap-{slug}.html. On a validation-discrepancy note in the output, still render (the page shows a discrepancy banner) but include the discrepancies in your report.open the written file. Report: the file path; milestone and task counts plus done percentage (roadmap.py stats); the unblocked todo tasks (roadmap.py ready — surfaced directly, no need to open the file); any validation discrepancies.roadmap-maintain runs (recompute --render); invoke this skill for the first render or an on-demand refresh.library/templates/roadmap-artefact.html; to change status colours, change the canonical table (STATUS_STYLE in roadmap.py + the conventions reference) — never patch a generated file.docs/artefacts/roadmap-*.html to .prettierignore, the same way .claude/roadmaps.json is already excluded — so regenerating the dashboard never fights the formatter.