implement-roadmap
/implement-roadmap
Run a locked roadmap in order. Use for /implement-roadmap. Writes each missing plan, then /implement-plan. Refuses a draft.
- 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
Run a locked roadmap in order. Use for /implement-roadmap. Writes each missing plan, then /implement-plan. Refuses a draft.
Original author description
Run a locked roadmap in order. Use for /implement-roadmap. Writes each missing plan, then /implement-plan. Refuses a draft.
How it works
SKILL.md has no level-two headings · 22 lines, 436 words
SKILL.md preview
---
name: implement-roadmap
description: >-
Run a locked roadmap in order. Use for /implement-roadmap. Writes each missing
plan, then /implement-plan. Refuses a draft.
---
# implement-roadmap
You run the roadmap in this session. Format: `node_modules/@workerstack/repo/references/roadmap-format.md`.
Refuse `status: draft`. Say it is not locked and stop. Do not write a plan.
Accept `locked` or `in-progress`. Set `in-progress` when you start. Same session. Do not spawn a subagent per slice.
For each open slice, in order:
1. If `Location` is absent, run `/write-plan` from that slice's line: its title and sentence on a pointer roadmap, its Title, Goal and Why on an old-shape one. Research the slice's decisions and Usage there; they go into the plan, not the roadmap. Read the roadmap's `## Previous mistakes` first and put each entry that touches this slice in the plan's Watch-outs. The lock is the approval: do not stop for plan approval. `/write-plan` picks the type and the `commit:` subject. The plan copies the roadmap's `strategy:` unless the slice's scope argues for another (heuristic in `/write-plan`). If it hits a plan-shaping question, stop and leave the roadmap `locked` or `in-progress`.
2. Set `Location` to the absolute plan path `/write-plan` reported. Do not write a second plan when Location is already set.
3. Run `/implement-plan` on that plan. It works in the plan's worktree `{serial}-{name}` and finishes it. Do not stop between slices.
4. Mark the slice `[x]` only after that plan's Verify is done.
5. Read that plan's `## Previous mistakes`. For each entry that changes the Order or a later slice (its sentence, or on an old-shape roadmap its Goal or Why, or a Decision), add `- slice: {what plan N found} → {what changed in the roadmap}` to the roadmap and make that change in the same save. Earlier entries stay.
A failed program Verify adds `- verify: …` to the roadmap. Stop on a blocker, a failed Verify, or a plan-shaping question.
When every slice and Verify are `[x]`, promote before `done`: the roadmap lives in `.tmp/` and is lost with it. For each roadmap entry that will happen again after this program (Write a lesson only for a mistake our normal workflow will hit again on other tasks. A one-time issue stays in the plan's Previous mistakes.), run `bun repo lessons match` on the files involved, then `hit` the matching lesson with `--evidence "roadmap {n}"` or write a new one (`node_modules/@workerstack/repo/references/lessons.md`). Write or hit it inside a worktree (`bun repo worktree add lesson-{slug}`), commit there, and run `cd <root> && bun repo worktree finish lesson-{slug}`. Then set `status: done`.
On a pointer roadmap the slice's why goes into the child plan's Context. On an old-shape roadmap the Why stays on the roadmap. Never add a Why heading to the child plan.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · workerstack/repo | 96 | MIT |
| workerstack/clients | 96 | MIT |
Database snapshot: 13.11.2026 · package version 86364ddd4560 (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
- 92review-roadmap
Review a roadmap in a fresh agent before lock. Use for /review-roadmap. - 82review-roadmap
Review a roadmap in a fresh agent before lock. Use for /review-roadmap. - 100implement
This skill should be used when the user asks to 'implement', 'implement a task', 'implement a plan', 'execute a plan', 'work on task', or 'start implementation'. - 95roadmap
Turn research into a phased roadmap of PR-sized work items, or pick up and work one item from an existing roadmap. Use "plan" mid-conversation when the user says there's enough to justify a roadmap ("write the roadmap", "let's turn this into a plan of PRs", "make a punchlist").… - 95decomposition-planning-roadmap
Creates step-by-step decomposition plans and migration roadmaps for breaking apart monolithic applications. Use when asking "what order should I extract services?", "plan my migration", "create a decomposition roadmap", "prioritize what to split", "monolith to microservices… - 87ab-start-roadmap
Execute a roadmap autonomously to completion — the layer above start-task. Use when a roadmap's tasks are planned and you want them run in dependency order, with independent tasks optionally in parallel. Verifies the dependency tree is planned before running; stops if a needed…