roadmap-visualizerlisted

Maintain a project's roadmap as a single canonical ROADMAP.md and render it as a scannable visual — a diagram plus a status table — instead of a wall of text. ROADMAP.md is the required source of truth: this skill always reads it before rendering and always writes changes back to it, so the plan never drifts into scattered chat messages. If no ROADMAP.md exists yet, it creates one. It picks the right diagram for the roadmap's shape: a flowchart for dependency- or evidence-gated sequences, a Gantt for time-bound plans, swimlanes for parallel workstreams. Use this whenever the user says "roadmap", "show roadmap", "where are we", "what's the plan", "status", "what's left", "update the roadmap", "visualise progress", "/roadmap", or "/status" — and proactively when a long discussion has changed the plan and the roadmap should be refreshed. Especially useful in long or multi-session chats where both the user and the assistant lose track of the plan.
Oldvictech/session-continuity · ★ 1 · AI & Automation · score 74

Install: claude install-skill Oldvictech/session-continuity

# Roadmap Visualizer Keeps one canonical roadmap file and turns it into a visual that can be read in seconds. It fights the wall-of-text problem — so it must not reproduce the wall. ## Operating principle **`ROADMAP.md` is the single source of truth — not the chat, not this skill.** Every render reads it first. Every agreed change is written back to it immediately. The chat is where the roadmap is discussed; `ROADMAP.md` is where it lives. These must never drift apart. --- ## The canonical file: ROADMAP.md The skill reads and writes this exact structure so the file stays machine-reliable and human-readable. The **status table is the canonical data**; the diagram is a generated view of it (regenerated from the table on every change, so they can't disagree). ```markdown # Project Roadmap _Last updated: YYYY-MM-DD · ROADMAP.md is the source of truth for project sequencing._ ## Shape <gated-sequence | time-bound | parallel-streams | decision-tree | status-board> ## Diagram <mermaid block — a generated VIEW of the Status table below; do not hand-edit> ## Status | # | Item | Status | Gated on / Next | |---|------|--------|-----------------| | 1 | ... | ✅ Done | — | | 2 | ... | 🔄 In flight | ... | | 3 | ... | ⏳ Pending | depends on #2 | | 4 | ... | ❌ Blocked | blocker: ... | | 5 | ... | 🅿️ Parked | ... | ## Constraints / Invariants - <locked decisions, immutable items, guardrails — omit section if none> ## Amendment log - YYYY-MM-DD: <what changed and why> ``` St