write-roadmap
/write-roadmap
Write an ordered program of plans under .repo/roadmaps/. Use for /write-roadmap. Stops for y, which locks and runs it.
- Author
- workerstack ↗
- Repository
- repo ↗
- Licence
- MIT
- Last repository change
- 13.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 13.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
Write an ordered program of plans under .repo/roadmaps/. Use for /write-roadmap. Stops for y, which locks and runs it.
Original author description
Write an ordered program of plans under .repo/roadmaps/. Use for /write-roadmap. Stops for y, which locks and runs it.
How it works
- Shape
SKILL.md preview
---
name: write-roadmap
description: >-
Write an ordered program of plans under .repo/roadmaps/. Use for
/write-roadmap. Stops for y, which locks and runs it.
---
# write-roadmap
You author the roadmap. First read `principle-sequence-verifiable-units` and follow it. Persist under `.repo/roadmaps/` via Write (hook runs `cli/scripts/persist-roadmap.ts`). All boxes `[ ]`. Status stays `draft` until the user approves with `i`.
Author a bare `strategy: {value}` line above `ROADMAP_NAME:`. Values and the heuristic: `/write-plan`. Add a bare `mode: {value}` line beside it on the same terms as `/write-plan`: `away` when this session runs `/away`, or the mode the person asked for. Under away the Stop hook runs the approval block's `i` once the review settles.
Before you ask the user, read `principle-never-block-on-the-human`. Ask only when the user alone can answer.
Two or more slices. One slice is `/write-plan`: say so and stop. Do not write a file.
Research until every slice is defensible. Ask only what changes the program. Then write the draft and stop.
After each save, spawn a fresh host agent whose prompt is only `/review-roadmap {n}` and the roadmap's absolute path (on Claude Code the `claude` agent type; scout is not the reviewer). Accept or reject each finding with a reason. Apply accepted ones to the same file and add one `- review: …` entry each to `## Previous mistakes`. Bump `reviews` by one in the save that settles the round, even with no findings: send a bare `reviews: {n}` line above `ROADMAP_NAME:`. The save denies a lower count.
On feedback, revise the same file (a Write of the saved path updates it in place), add a `- feedback: …` entry for what the user rejected and what changed, and run `/review-roadmap` again. Never edit or drop an earlier entry.
On `i`, a short yes or an `i` code, set `status: locked` on the same file, then run `/implement-roadmap {n}`. On `h` or an `h` code, the hook writes the handoff: tell the person to run the `/pickup {serial}` it names in a fresh session, and do no work here. The save denies the lock while `reviews` is 0. Do not run `/write-plan` or `/implement-plan` from this skill.
Report the serial, the absolute path, the slice titles in order, the top risk, and the review findings you rejected with why. Stop and end the reply with the approval block from `/write-plan` for this roadmap, headed `roadmap {n} · {s}`, in its queue form when other reviewed plans or roadmaps wait. Only after the review settled (`reviews` bumped since the review spawn); the Stop hook blocks it otherwise. Ask for approval no other way.
## Shape
Shape and row rules: `node_modules/@workerstack/repo/references/roadmap-format.md`.
`ROADMAP_NAME:` is 3–6 words. The hook turns it into the slug and the frontmatter. Do not invent `serial`, `created`, or `source`.
No Type. No Commit. Those go on the child plan.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · workerstack/repo | 85 | MIT |
| workerstack/clients | 100 | MIT |
Database snapshot: 13.11.2026 · package version bada60cdfbd8 (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
- 100roadmap-writing
Use when authoring or rewriting a roadmap in agents/roadmaps/ — phases, goal, acceptance criteria, council notes; fires even on 'write a plan for X' / 'draft a roadmap'. - 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. - 100nav-roadmaps
Show every roadmap document in the project's .agent/ tree as one table (title, path, kind, last date, status line) plus per-section ticket counts for ticket-table roadmaps. Auto-invoke when user says "show roadmaps", "list roadmaps", "which roadmaps are open", "roadmap table",… - 90planning-create-roadmap
Use this skill when the user says 'create roadmap', 'roadmap', 'product roadmap', 'feature roadmap', 'quarterly roadmap', 'release plan', 'timeline', 'roadmap planning'. Build a structured product roadmap with themes, timeline, prioritization, and communication plan. Do NOT use… - 100roadmap-generator
Generate roadmap generator operations. Auto-activating skill for Enterprise Workflows. Triggers on: roadmap generator, roadmap generator Part of the Enterprise Workflows skill category. Use when working with roadmap generator functionality. Trigger with phrases like "roadmap…