roadmap
/roadmap
Use to keep the portfolio layer above individual features — one living docs/roadmap.md of outcomes, structured Now / Next / Later, that links to per-feature docs without duplicating them. Triggers on "roadmap", "what's next", "prioritize the roadmap", "add to the roadmap", "show the roadmap", "/sdlc:roadmap", "роадмеп", "що далі", "пріоритети", "додай у roadmap". Captures a candidate as an outcome/problem (lands in Next/Later, RICE-scored), promotes/demotes between horizons, and renders the board. It is outcome-altitude — NOT a feature list or a dated Gantt; the solution lives in the feature's
- Author
- genkovich ↗
- Repository
- sdlc ↗
- Licence
- MIT
- Last repository change
- 25.10.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 25.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use to keep the portfolio layer above individual features — one living docs/roadmap.md of outcomes, structured Now / Next / Later, that links to per-feature docs without duplicating them. Triggers on "roadmap", "what's next", "prioritize the roadmap", "add to the roadmap", "show the roadmap", "/sdlc:roadmap", "роадмеп", "що далі", "пріоритети", "додай у roadmap". Captures a candidate as an outcome/problem (lands in Next/Later, RICE-scored), promotes/demotes between horizons, and renders the board. It is outcome-altitude — NOT a feature list or a dated Gantt; the solution lives in the feature's
Triggers from the description
Original author description
Use to keep the portfolio layer above individual features — one living docs/roadmap.md of outcomes, structured Now / Next / Later, that links to per-feature docs without duplicating them. Triggers on "roadmap", "what's next", "prioritize the roadmap", "add to the roadmap", "show the roadmap", "/sdlc:roadmap", "роадмеп", "що далі", "пріоритети", "додай у roadmap". Captures a candidate as an outcome/problem (lands in Next/Later, RICE-scored), promotes/demotes between horizons, and renders the board. It is outcome-altitude — NOT a feature list or a dated Gantt; the solution lives in the feature's
How it works
- Owner
- Inputs
- Protocol
- Sync hooks (delivery keeps it current — anti-drift)
- Definition of Done
- Anti-patterns
- References & template
SKILL.md preview
--- name: roadmap description: >- Use to keep the portfolio layer above individual features — one living docs/roadmap.md of outcomes, structured Now / Next / Later, that links to per-feature docs without duplicating them. Triggers on "roadmap", "what's next", "prioritize the roadmap", "add to the roadmap", "show the roadmap", "/sdlc:roadmap", "роадмеп", "що далі", "пріоритети", "додай у roadmap". Captures a candidate as an outcome/problem (lands in Next/Later, RICE-scored), promotes/demotes between horizons, and renders the board. It is outcome-altitude — NOT a feature list or a dated Gantt; the solution lives in the feature's PRD, not here. write-prd promotes an item to Now; ship-feature moves it to Shipped — so delivery keeps the roadmap in sync. Output: docs/roadmap.md (repo-root, one file, shared across all features). triggers: - /sdlc:roadmap - roadmap - what's next - prioritize the roadmap - add to the roadmap - show the roadmap - роадмеп - що далі - пріоритети - додай у roadmap --- # Skill: roadmap The **portfolio layer** above the per-feature pipeline. The SDLC toolkit builds one feature at a time under `docs/features/<slug>/`; `roadmap` is the single living view *across* features — what we're doing now, what's next, what's directional later — kept at **outcome altitude** (the "why"/problem), with each item linking to its feature folder rather than restating the PRD. A roadmap is **direction, not a promise**, and **not a release plan**: feature-and-date roadmaps are the biggest source of waste — they project false certainty, go stale fastest the further out they reach, and commit to solutions before discovery. So this roadmap encodes *decreasing certainty over time* and never carries dates. Repo-level utility (like `map-architecture`) — one file serves the whole repo. ## Owner Whoever owns product direction (PM / lead / the solo maintainer). They decide what's Now/Next/Later; the pipeline keeps statuses in sync. ## Inputs - (Optional) a candidate to capture (an outcome/problem in one line), or an action: prioritize / promote / demote / render. - `docs/features/*/` — to link items to existing feature folders and read their status. ## Protocol 1. **Lazy-create.** If `docs/roadmap.md` is absent, copy [`./templates/roadmap.md`](./templates/roadmap.md) there (the non-commitment disclaimer + the Now / Next / Later / Shipped sections, **each rendered as a table** — one row per item). One file, repo root `docs/`. 2. **The three horizons — content type changes per horizon** (this is the load-bearing rule, not feature-everywhere): - **Now** — committed work whose `docs/features/<slug>/` PRD exists and is being built. Item = outcome one-liner + link to the feature folder + a status (designing / implementing / review). Promoted here only after `write-prd` (it's spec'd + committed). - **Next** — problems/opportunities deliberately **NOT yet spec'd** — an outcome/problem one-liner + a RICE score, no feature folder yet. This is the prioritized candidate pool. - **Later** — outcomes/themes, directional only. No features, no scores. 3. **Capture a candidate** → add to **Next** (or Later) as an outcome/problem, RICE-scored. **Never** write a solution/feature PRD here — that's `write-prd`'s job when the item is pulled into Now. 4. **Prioritize (RICE).** For Next candidates, score `RICE = (Reach × Impact × Confidence) ÷ Effort` (Impact 3/2/1/0.5/0.25; Confidence 100/80/50%; Effort in person-weeks) → one sortable number; order Next by it descending. RICE is a guide, not a gate — the owner can override. → [`./templates/roadmap.md`](./templates/roadmap.md) shows the columns. 5. **Promote / demote.** Move items between horizons as certainty changes. Promote Next→Now only when the item is about to be `write-prd`'d (committed). Demote freely; far-out items stay coarse. 6. **Render / write + commit + handoff.** Update `docs/roadmap.md`, set `updated_at`, propose commit `roadmap: <what changed>`. Then **emit the stage-handoff block** per [`../_shared/handoff.md`](../_shared/handoff.md) (utility variant) — *What I did* + *Review* (`docs/roadmap.md`) + *Run next*: resume your backbone stage; `/clear` optional. ## Sync hooks (delivery keeps it current — anti-drift) - **`write-prd`** registers its feature on the roadmap and promotes the item to **Now** (outcome one-liner + link to the new `docs/features/<slug>/` + status). A brand-new feature with no prior candidate is added directly to Now. - **`ship-feature`** moves the item to **Shipped** (date + link to the PR/changelog) and removes it from Now. Because the pipeline stages themselves update the roadmap, it stays current without separate upkeep — the same mechanism GitHub's public roadmap uses (ship → mark shipped → close). ## Definition of Done - `docs/roadmap.md` exists with the disclaimer + Now / Next / Later (+ Shipped), items at **outcome altitude**, each Now/Shipped item **linking** to its `docs/features/<slug>/` (no PRD duplication). - Next is RICE-ordered; no dates anywhere; no feature-level detail in Later. - `updated_at` reflects the change. ## Anti-patterns - **A feature-and-date roadmap / a Gantt.** Items are outcomes/problems; dates are absent; the solution lives in the PRD. This is the cardinal sin the research names as the biggest source of waste. - **Duplicating the PRD** on the roadmap. Link to `docs/features/<slug>/`; the roadmap holds the *why*, not the *how*. - **Over-detailing Later.** Far-out items are directional one-liners — detailing them is fiction that goes stale. - **Roadmap-as-promise.** Keep the disclaimer; near-term is firm, far-term will change. - **Promoting to Now before `write-prd`.** Now = committed + spec'd; un-spec'd work stays in Next. - **Letting it rot.** The `write-prd`/`ship-feature` hooks keep it live — don't bypass them with a stale hand-maintained list. ## References & template - [`./templates/roadmap.md`](./templates/roadmap.md) — the living-roadmap scaffold (disclaimer + Now/Next/Later/Shipped + RICE columns). - [`../_shared/handoff.md`](../_shared/handoff.md) — stage-handoff block format (utility variant).
Files in this package (2)
- SKILL.md 6 KB
- templates/roadmap.md 2 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · genkovich/sdlc | 90 | MIT |
| minanyang/10x-agent | 100 | MIT |
| iuliandita/skills | 100 | MIT |
| cloudposse/atmos | 100 | Apache-2.0 |
| raccoon-office/box-agent | 100 | MIT |
| Mosin112/pm-harness | 100 | MIT |
| facebookresearch/autoform-bot | 100 | MIT |
| rafagomes/ai-workflow | 100 | MIT |
| hashintel/labs | 100 | MIT |
Database snapshot: 13.11.2026 · package version fed2525f95ce (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90create-roadmap
Create a Now/Next/Later outcome-oriented roadmap when the user asks to plan a roadmap, prioritize features, or define product direction - 100outcome-roadmap
Transform output-based feature lists into outcome-driven Now/Next/Later roadmaps using the "so what?" technique. Use when converting a feature-list roadmap to outcomes, communicating product strategy, or running quarterly planning. - 85pm-roadmap
Create or critique a product roadmap — outcome-oriented, theme-based, confidence-aware (Now-Next-Later) roadmaps tied to strategy, instead of dated feature lists. Gates format and detail by audience and planning horizon. Trigger when the user asks to build, write, review, or… - 100helm-plan
Use when asked to build a product roadmap, prioritize a backlog, decide what to build next, or sequence a list of feature ideas. Examples: "what should we build next", "prioritize this backlog", "make a roadmap", "RICE score these features". - 100outcome-roadmap
Transform an output-focused roadmap (feature list) into an outcome-focused one. Rewrites initiatives as outcome statements reflecting user and business impact. Use when a roadmap lists features instead of results, when making a roadmap more strategic, or when communicating what… - 100helm-plan
Use when asked to build a product roadmap, prioritize a backlog, decide what to build next, or sequence a list of feature ideas. Examples: "what should we build next", "prioritize this backlog", "make a roadmap", "RICE score these features".