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
- clients ↗
- Licence
- MIT
- Last repository change
- 10.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 10.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, 307 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: `.rulesync/reference/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 Title, Goal, and Why. 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. 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. 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 a Decision, the Order, or a later slice's Goal or Why, 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, run `node .rulesync/scripts/lessons.mjs match` on the files involved, then `hit` the matching lesson with `--evidence "roadmap {n}"` or write a new one (`.rulesync/reference/lessons.md`). Then set `status: done`.
A slice's Why stays on the roadmap. Do not add a Why heading to the child plan.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · workerstack/clients | 96 | MIT |
| workerstack/repo | 96 | MIT |
Database snapshot: 13.11.2026 · package version 2c5653229026 (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. - 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… - 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… - 90test-automation-roadmap
Decide what to automate next and in which order: score candidate test cases or journeys by frequency of execution, business risk, stability of the feature, cost to automate and flakiness risk, choose the right level (unit, API, UI), and produce a 3-month automation roadmap. Use…