roadmaplisted

Tracks features across their lifecycle in a live, per-repo roadmap — every RD, plan, and task and the lifecycle stage each is in. Layout-aware: a single plans/00-roadmap.md in flat layout, or a two-tier per-feature + portfolio roadmap under codeops/ in nested layout. Use when the user says "roadmap", "make_roadmap", "update_roadmap", "review_roadmap", "show_roadmap", "archive_roadmap", or "compact_roadmap". Covers six actions: make_roadmap (create + seed rows from disk), update_roadmap (re-infer stages, sync to disk, cascade to the portfolio), review_roadmap (read-only health check for drift/broken links), show_roadmap (read-only status overview — progress, stages, and next steps), archive_roadmap (move a completed feature to the archive), and compact_roadmap (slim a bloated roadmap: strip the legacy Notes log and trim fat cells). Detects the action from the user's phrasing or arguments and branches. The roadmap is the cross-session source of truth at the RD/plan altitude, above any single execution plan.
blendsdk/claude-codeops · ★ 4 · AI & Automation · score 75

Install: claude install-skill blendsdk/claude-codeops

# roadmap — Live Feature-Set Roadmap Keeper > **CodeOps Skills Version**: 3.20.0 ## Resolve paths first (layout-aware) Before any action, determine the layout via **[../../_shared/layout-convention.md](../../_shared/layout-convention.md)**: - **Flat layout** (no `codeops/.codeops.yml`): a single roadmap at `plans/00-roadmap.md`. Behaves **exactly as flat layout always has** — everything below that mentions "the roadmap" means this one file, and the portfolio tier does not exist (its cascade steps are inert). - **Nested layout** (marker present): **two tiers** — a per-feature roadmap at `codeops/features/<f>/00-roadmap.md` and a **portfolio roadmap** at `codeops/00-roadmap.md` (one row per feature, auto-cascaded). In nested layout the skill asks/confirms the **target feature** before acting on a per-feature roadmap, and creates the feature folder lazily (never guesses). The roadmap is a living document that tracks an entire **feature** at a higher altitude than any individual execution plan. Where `99-execution-plan.md` tracks the tasks *within one feature*, the roadmap tracks *every requirement (RD), plan, and task* and the lifecycle stage each is in. It is the user's cross-session lifeline: open it to see what is done, in flight, blocked, or in backlog. It never replaces the execution plan; it indexes and summarizes across many of them. ## Action dispatch Detect the action from the user's phrasing or argument and branch: | Trigger | Action | |---------|---