roadmap
/roadmap
Picks the next task from a project's ROADMAP.jsonl and crafts its handoff prompt, or adds, corrects, accepts, resumes, defers, archives or restores entries, reviews status, and checks the file's structural health. Ranks candidates deterministically by dependencies and file-touch collisions and shows why each is where it is. Use when the user asks what to work on next, wants to add or fix a roadmap entry, or wants roadmap status. Not for first-time setup (init), checking entries against the code (survey), or a prompt with no roadmap entry (craft-prompt).
- Author
- V-Songbird ↗
- Repository
- foreman ↗
- Licence
- MIT
- Last repository change
- 12.11.2026
Assessment and security
- Files in this package
- 24
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 12.11.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
Picks the next task from a project's ROADMAP.jsonl and crafts its handoff prompt, or adds, corrects, accepts, resumes, defers, archives or restores entries, reviews status, and checks the file's structural health. Ranks candidates deterministically by dependencies and file-touch collisions and shows why each is where it is. Use when the user asks what to work on next, wants to add or fix a roadmap entry, or wants roadmap status. Not for first-time setup (init), checking entries against the code (survey), or a prompt with no roadmap entry (craft-prompt).
Arguments
/roadmap <optional — a task description to add, or a hint about what to pick next>
Original author description
Picks the next task from a project's ROADMAP.jsonl and crafts its handoff prompt, or adds, corrects, accepts, resumes, defers, archives or restores entries, reviews status, and checks the file's structural health. Ranks candidates deterministically by dependencies and file-touch collisions and shows why each is where it is. Use when the user asks what to work on next, wants to add or fix a roadmap entry, or wants roadmap status. Not for first-time setup (init), checking entries against the code (survey), or a prompt with no roadmap entry (craft-prompt).
How it works
- Branch: Pick the next task
- Branch: Add a task
- Branch: Correct a task
- Branch: Review status
- Branch: Check the roadmap
SKILL.md preview
---
name: roadmap
description: "Picks the next task from a project's ROADMAP.jsonl and crafts its handoff prompt, or adds, corrects, accepts, resumes, defers, archives or restores entries, reviews status, and checks the file's structural health. Ranks candidates deterministically by dependencies and file-touch collisions and shows why each is where it is. Use when the user asks what to work on next, wants to add or fix a roadmap entry, or wants roadmap status. Not for first-time setup (init), checking entries against the code (survey), or a prompt with no roadmap entry (craft-prompt)."
when_to_use: "Trigger when the user asks what to work on next, wants to add something to the roadmap, wants to fix or reword an entry that already exists, wants to see roadmap status, thinks the roadmap file itself is broken, says \"what's next\", \"pick a task\", \"add to the roadmap\", \"that task's description is wrong\", \"roadmap status\", \"my roadmap is broken\", or invokes /foreman:roadmap."
argument-hint: "<optional — a task description to add, or a hint about what to pick next>"
allowed-tools: AskUserQuestion, Read, Write, Bash, PowerShell, TaskCreate, TaskUpdate, Agent, SendMessage
---
# foreman:roadmap — pick, add to, correct, review, or check the project roadmap
Foreman runs in Claude Code, Codex and Antigravity. Every step applies to every host unless it names one. Read [the shared runtime](../foreman/runtime.md) first: it covers plugin paths, JSON payloads, questions and authorization for every host.
All reads/writes to `ROADMAP.jsonl` at the project root go through
`${CLAUDE_PLUGIN_ROOT}/scripts/roadmap.js` — never read or edit the file
directly, the script enforces id computation and parse-before/after-write
mechanically — run it as `roadmap.js <subcommand> --help` (for example
`roadmap.js list --help`) for that subcommand's shape. Read the
**Fields** section of [roadmap-schema.md](../../roadmap-schema.md)
(`${CLAUDE_PLUGIN_ROOT}/roadmap-schema.md`) if you need field semantics beyond
what's obvious from the names.
**Pre-check**: if `ROADMAP.jsonl` doesn't exist at the project root, offer to
set the project up with [init](../init/SKILL.md) (`/foreman:init` in Claude
Code) and stop here. When the user's request already includes setup, run init
directly instead.
A request the `foreman` entrance routed here names its branch: go straight to
that branch below. A direct `/foreman:roadmap` call, or a request handed over
without a branch, reads [menu.md](menu.md)
(`${CLAUDE_PLUGIN_ROOT}/skills/roadmap/menu.md`) first: it holds the menu, the
phrasings that pick a branch without it, requests to archive or restore
finished work, and how its questions are logged.
---
## Branch: Pick the next task
Read [pick.md](pick.md) (`${CLAUDE_PLUGIN_ROOT}/skills/roadmap/pick.md`) and follow it.
---
## Branch: Add a task
Read [add.md](add.md) (`${CLAUDE_PLUGIN_ROOT}/skills/roadmap/add.md`) and follow it.
---
## Branch: Correct a task
Read [correct.md](correct.md) (`${CLAUDE_PLUGIN_ROOT}/skills/roadmap/correct.md`) and follow it.
---
## Branch: Review status
Read [status.md](status.md) (`${CLAUDE_PLUGIN_ROOT}/skills/roadmap/status.md`) and follow it.
---
## Branch: Check the roadmap
Read [doctor.md](doctor.md) (`${CLAUDE_PLUGIN_ROOT}/skills/roadmap/doctor.md`) and follow it.
Files in this package (24)
- SKILL.md 3 KB
- accept.md 2 KB
- add.md 3 KB
- close-increments.md 3 KB
- correct.md 3 KB
- defer.md 1 KB
- delivery-agent.md 5 KB
- delivery-clipboard.md 2 KB
- delivery-split.md 4 KB
- delivery.md 5 KB
- destination-question.md 11 KB
- doctor.md 4 KB
- hint.md 1 KB
- increment-review.md 7 KB
- menu.md 3 KB
- pick.md 16 KB
- prepare-increments.md 5 KB
- reconcile.md 2 KB
- resume-increments.md 5 KB
- resume.md 3 KB
- status.md 2 KB
- agents/openai.yaml 1 KB
- assets/icon.png 18 KB
- assets/icon.svg 1 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · V-Songbird/foreman | 95 | 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 09f9bdc523c2 (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
- 96sync-roadmap
Reconcile ROADMAP.md checkbox state against on-disk SUMMARY.md presence. Default: silently corrects drift; --dry-run previews; --interactive prompts per change. Triggers on: "sync roadmap", "reconcile roadmap", "fix roadmap drift", "is the roadmap accurate". - 86roadmap-planning
Use when preparing a roadmap or running a planning session for a legwork project, such as "plan the next roadmap for <project>", "prepare a roadmap", or any session whose output is a design doc, a tracker Roadmap N and a queued /fanout prompt. - 95roadmap-workflow
Follow and maintain an agentic-roadmap plan in roadmap/. Use when a repo has roadmap/roadmap.yaml, when planning work in that repo (including plan mode), or when asked what to work on next. Choose ready tasks, track work through branches and commits, and submit new plans as importable task tables. - 92review-roadmap
Review a roadmap in a fresh agent before lock. Use for /review-roadmap. - 82roadmap-update
Propose and apply the roadmap change that a request implies — new task, new epic, a task moved to another milestone, a change of scope, or work dropped — through scripts/roadmap.py, after the maintainer confirms. Use whenever a request adds, changes or drops planned work, or… - 82roadmap-update
Propose and apply the roadmap change that a request implies — new task, new epic, a task moved to another milestone, a change of scope, or work dropped — through scripts/roadmap.py, after the maintainer confirms. Use whenever a request adds, changes or drops planned work, or…