AGENT SKILL

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 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).

License 许可
MIT
最近更新
2026-11-12
Stars
★ 15
Forks
13

01 前言 Front Matter

name
roadmap
triggers
[ "/sdlc:roadmap", "roadmap", "what's next", "prioritize the roadmap", "add to the roadmap", "show the roadmap", "роадмеп", "що далі", "пріоритети", "додай у 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).

02 资源文件 1

03 SKILL.md 正文

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 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 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 (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

04 同仓库更多 Skills

genkovich
genkovich/agentic-engineering-course-public

release

Run the whole local release pipeline in order, stopping at each human gate. Triggers on "run the release", "prepare a release", "/release", "зроби реліз", "підготуй реліз". Drives the four stages back to back — bump-version → curate-changelog → release-notes → check-docs-drift — pausing after each so the human reviews the diff before the next stage. Prepares everything in the working tree; never tags, commits, or pushes. The tag push (which fires CI) stays the human's action.

★ 15
genkovich
genkovich/agentic-engineering-course-public

release-notes

Draft partner-facing release notes from the same commits as the changelog. Triggers on "draft release notes", "release notes for the next version", "/release-notes", "нотатки релізу", "release notes партнеру". Same input as curate-changelog, different audience and tone: a short, benefit-first narrative for a user or partner — "what's new for you" — not a categorized engineer's list. Keeps only changes a user actually notices; drops internal refactors and tooling. Prints the notes to the chat to seed a GitHub Release description or a partner announcement. Writes no file.

★ 15
genkovich
genkovich/agentic-engineering-course-public

curate-changelog

Curate the [Unreleased] section of docs/CHANGELOG.md from git history. Triggers on "curate the changelog", "update the changelog", "/curate-changelog", "онови changelog", "курування журналу". Reads git log since the last tag, FILTERS out what a reader never feels (test/ci/chore/merge), GROUPS commits about one feature into one bullet, and REWRITES technical subjects into plain language under the six Keep a Changelog categories (Added/Changed/Deprecated/ Removed/Fixed/Security). The result must have FEWER lines than the raw log — that is the proof of curation, not a dump. Leaves the edit in the working tree; never commits or pushes.

★ 15
genkovich
genkovich/agentic-engineering-course-public

codify-rule

Turn a repeated mistake into a durable, path-scoped rule in .claude/rules/. Triggers on "codify this rule", "make a rule so this doesn't happen again", "/codify-rule", "закодифікуй правило", "петля помилка-правило". Use only when the same mistake showed up TWICE (twice = a pattern, once = noise). Names the wrong shape and the right shape with one short example of each, scopes the rule to the paths that matter, and leaves the edit in the working tree so the next agent on this repo inherits the fix. Edits only .claude/rules/; never commits or pushes.

★ 15
genkovich
genkovich/agentic-engineering-course-public

check-docs-drift

Find and fix where docs/api.md fell behind the code. Triggers on "check for doc drift", "is the API doc up to date", "/check-docs-drift", "перевір дрейф документації", "docs drift". Runs the deterministic scripts/check-docs-drift.py (parses the public NoteBook methods with ast, compares to what docs/api.md documents — NO LLM finds the gap), reports the drift, and PROPOSES the doc edit that closes it. The gap is found by parsing; the agent writes the missing documentation in the doc's existing style. Edits only docs/; never commits or pushes.

★ 15
genkovich
genkovich/agentic-engineering-course-public

bump-version

Decide and apply the next semver for a release. Triggers on "bump the version", "what version is next", "/bump-version", "простав версію", "яка наступна версія". Reads the next number from the deterministic scripts/next-version.sh (NEVER guesses it), explains in plain language WHICH part moved and why (e.g. "MINOR, because a feat landed: filter notes by tag"), edits the version line in pyproject.toml, and proposes the matching `git tag vX.Y.Z`. The number is decided by a rule; the agent explains and applies — the human confirms the tag. Never pushes a tag itself.

★ 15