roadmap
Use to break a product idea into incremental steps and keep that decomposition living — one docs/roadmap.md with a destination sentence, the steps table (source-anchored, sized XS–XL or marked fog), the fog vocabulary (what's in scope but not yet formulated, what never graduates, which decisions are still open and who owns them), the dependency graph that owns every edge, and the execution path: dependency-respecting waves that show what can run in parallel (e.g. in worktrees) and what must wait. Triggers on "roadmap", "break this down", "decompose the idea", "what depends on what", "execution plan", "/sdd:roadmap", "роадмап", "розбий ідею на кроки", "що від чого залежить", "що можна паралельно". Takes any scope — a whole product, an epic, or a single feature. Reads docs/idea-brief.md or a PRD (+ design canon and architecture map when they exist; neither is required). It decomposes and orders — it is NOT a prioritization scorecard and NOT a dated Gantt; specify/ship keep step statuses
genkovich · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add genkovich/sdd --skill roadmap技能说明
name: roadmap model: inherit effort: medium agents: [] description: > Use to break a product idea into incremental steps and keep that decomposition living — one docs/roadmap.md with a destination sentence, the steps table (source-anchored, sized XS–XL or marked fog), the fog vocabulary (what's in scope but not yet formulated, what never graduates, which decisions are still open and who owns them), the dependency graph that owns every edge, and the execution path: dependency-respecting waves that show what can run in parallel (e.g. in worktrees) and what must wait. Triggers on "roadmap", "break this down", "decompose the idea", "what depends on what", "execution plan", "/sdd:roadmap", "роадмап", "розбий ідею на кроки", "що від чого залежить", "що можна паралельно". Takes any scope — a whole product, an epic, or a single feature. Reads docs/idea-brief.md or a PRD (+ design canon and architecture map when they exist; neither is required). It decomposes and orders — it is NOT a prioritization scorecard and NOT a dated Gantt; specify/ship keep step statuses in sync as features move.
Skill: roadmap
The decomposition layer between the idea and the per-feature pipeline. SDD builds one feature
at a time under docs/features/<slug>/; roadmap answers the question that comes before any
feature: where are we going, how does the idea break into steps, what depends on what, and in
which order — and in what parallel lanes — do we walk them. One living docs/roadmap.md,
repo-level utility (like survey).
Scope is whatever you bring. A whole product, one epic, or a single feature — the unit of the input does not change the unit of the output. A one-feature request gets decomposed the same way; there are simply fewer steps, and «fewer» is a legitimate answer. The skill never refuses a request for being too small, and never inflates one to look like a product plan.
Five load-bearing properties, in priority order:
- A destination — one sentence for what is true once the last step ships. Without it the steps are a list of work with nothing to be a decomposition of.
- Steps — the idea decomposed into incremental, source-anchored slices (each row cites the
brief/PRD section it comes from; size XS–XL per
../_shared/size-matrix.md). - A word for what you don't know yet.
SizeisXS…XLorfog, in the same cell, because they answer the same question and only one of them can be true: sizing something nobody has formulated yet is how an estimate becomes a lie. Fog lives in## Not yet specifieduntil a recon pass sharpens it, and then the row tradesfogfor a real size. - Dependencies — an explicit graph, and the graph is where edges live. Every edge has a one-line reason (data model, UI zone, auth precondition). No edge without a real blocker, and no second copy of the edges in a column that could disagree with it.
- Execution path — waves that respect the graph: wave N only contains steps whose deps are in earlier waves, and steps inside one wave are conflict-safe in the codebase (different modules / UI zones — so they can run as parallel worktree lanes). Each wave row names the zone.
Not here: RICE or any scoring (order IS the prioritization), dates (a decomposition, not a
promise), solution detail (lives in the feature's spec). Question phrasing →
../_shared/ask-style.md; prose follows artifact_language, table
structure and the Status / Size values stay English → ../_shared/artifact-language.md.
Owner
Whoever owns product direction (PM / lead / the solo maintainer).
Inputs
- Required — the idea source:
docs/idea-brief.md(written byinterview) / a PRD / a vision note (ask which, if several). This is the only hard input. - Optional —
docs/architecture-map.md(written bysurvey): zones for conflict-safety. Its absence costs precision in one column, not the roadmap. - Optional —
docs/design-system.md. - Optional — existing
docs/features/*/+ existingdocs/roadmap.md— current statuses.
Protocol
-
Locate sources. Find the idea source (
docs/idea-brief.mdfirst, then PRD candidates). None found → say so and STOP: a roadmap without a source is fiction, and the fix is one command —/sdd:interviewwrites that brief. That is the only hard stop.docs/architecture-map.mdis optional and never a gate. Present → its module inventory supplies the zones in## Execution path. Absent → the roadmap is written anyway, every zone that is not an existing path is marked(new), and the handoff says plainly that the waves are a first cut worth re-cutting after/sdd:surveyfills the map. A missing map degrades one column; it does not block the decomposition.Greenfield (empty repo, no
docs/features/*at all): the first step isscaffold. Every other step assumes a skeleton to build into — a repo with no module layout, no test harness and no migration tooling cannot receive step 1 as written. Its source anchor is the foundation section ofdocs/architecture-map.mdwhen the map exists, otherwise the brief itself (the project has to exist before anything in the brief can be built).If
docs/roadmap.mdexists, this run updates it (statuses, new steps, re-waving) — never silently rebuilds. A file written before 2.2 carries aDepends oncolumn the template no longer has; this run folds it away — the edges it held move into the dependency graph, which is now the one place edges live. Say so in the handoff, so the dropped column reads as a migration rather than lost data. -
Decompose — yourself, with the owner. Cutting an idea into steps is a live exchange with the person who holds the intent; it is not delegable, and a