← ClaudeAtlas

roadmaplisted

Put an initiative's features in the order they can actually be built, and keep that order as the one place anyone can read how far along the work is. Use it when the question is order — "what should we do first?", "what's the order here?", "sequence these features", "we have five features, plan the rollout" — and equally when the question is progress: "how far along are we on the plugin work?", "where are we on this?", "track this initiative". One feature is enough; there is no two-feature floor, so "there's only one thing here, a roadmap is overkill" is the wrong call and leaves the bet above it with nothing carrying it. Without one, progress lives scattered across PRs and issue states and nobody can answer the question at all. Do NOT use it to break a single feature into implementation issues (`/plan`), to work out that feature's requirements (`/scope`), or to make the case for the bet the sequence serves (`/strategy`, or `/charter` for both at once).
tsukumogami/shirabe · ★ 0 · AI & Automation · score 67
Install: claude install-skill tsukumogami/shirabe
!`bash ${CLAUDE_PLUGIN_ROOT}/scripts/skill-preflight.sh roadmap 2>&1 || true` @.claude/shirabe-extensions/roadmap.md @.claude/shirabe-extensions/roadmap.local.md # Roadmap Documents Roadmap documents sequence features into a coordinated initiative. They capture the theme (why these features belong together), the features themselves, dependency relationships, sequencing rationale, and progress. They are the last link in the strategic chain (VISION -> STRATEGY -> ROADMAP): a roadmap's upstream is the STRATEGY it sequences -- its immediate neighbour, and not the VISION two levels up, which this skill never writes even though the validator tolerates it in an existing corpus (see `references/roadmap-format.md`) -- and downstream of it sit the BRIEFs and PRDs that frame and define individual features in detail. ## What a Roadmap Is For Sequencing is only half a roadmap's job. The other half matters just as much: - **It is the progress ledger for a strategy's execution.** The per-feature status in the Features and Progress sections is the only place that records how far along the work is, and the completion cascade updates it as downstream plans land. Without a roadmap, a strategy has no ledger. - **It is the only bridge from the strategic chain to the tactical one.** `/brief` is framed against a ROADMAP -- never a STRATEGY, and never a PRD, which sits downstream of a BRIEF rather than above it. The brief reads the roadmap and records the roadmap's own parent, ofte