Menu
Chart or resequence a multi-unit work horizon — destination, thin claimable streams, order, and NEXT — user-approved map for continue to consume
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Backlog-scale orchestration on top of /workflow — drives PM items through refine → plan → implement → review → local-merge via role-specialized sub-agents dispatched in parallel waves, each item isolated in its own git worktree. Bare /swarm summarizes state; /swarm <goal> runs the orchestrator; /swarm:setup sets up the charter and .agent-tools/ umbrella; /swarm:continue resumes a paused run.
Capture durable knowledge from any engineering work — debugging solutions, refactors, features, design decisions, reusable patterns — and maintain memory quality so each unit of work compounds the next
Principal workflow entry — resolve portfolio mode (swarm resume/handoff or unit state machine), drive work without inventing path; hard-stop when path is not established
Initialize and maintain planning root (.agent-tools/planning preferred), conventions (tracks, gates, integration), runs ledger scaffold, and shared memory under .agent-tools/memory/ (AGENTS.md memory-link) for the workflow family.
Parent skill for the workflow family — principal session entry is /workflow:continue (also bare /workflow). Horizon mapping, brainstorm, refine, plan, execute, review, audit, compound. Vertical-slice and deliverable-partition modes.
Detect gaps in the canonical skill corpus, propose targeted improvements, validate changes, and present for review. Inventories src/** skill trees; optional run-ledger seeds for process IP gaps.
| name | workflow:roadmap |
| description | Chart or resequence a multi-unit work horizon — destination, thin claimable streams, order, and NEXT — user-approved map for continue to consume |
| argument-hint | [optional: initiative/goal text, 'update', 'resequence', or path to existing roadmap] |
| user-invocable | true |
/workflow:roadmap)Chart a multi-unit body of work: name the destination, list claimable streams (or order
existing units), set dependencies/parallelization, and leave a consumable NEXT pointer for
/workflow:continue.
Plan, don't do. This skill produces a map and order — not ACs, tasks, or code.
Shared invariant: no durable stream list or committed NEXT without an explicit user approval turn. Draft; user approves before write.
$ARGUMENTS
| Input | Meaning |
|---|---|
| Empty / goal text | Chart a new map or open an existing one for update |
update / resequence | Load existing map; revise order/streams with approval |
| Path to roadmap / workstream dir | Target that artifact |
/workflow:continue.Not this skill
/workflow:brainstorm/workflow:refine/workflow:plan/workflow:continueIf charting shows one claimable unit and no multi-stream structure, stop without writing a
map. Offer /workflow:brainstorm or /workflow:refine instead.
A claimable unit is something continue can pick: a stable slug/name, a planning/<item>/ path
(optional at claim time), a PM issue id, or an explicit stub the user accepts as next work —
not a phase of one story and not an AC list. Missing planning dir does not make a named
stream unclaimable — continue claims it and enters refine/plan, which create the shell.
Pick early (state it to the user):
| Mode | When | Focus |
|---|---|---|
| Decompose | Few/no claimable units yet | Destination + thin streams that will become units |
| Sequence | Units already exist (PM, planned session-states, workstreams) | Order only (→ / ∥); do not invent a new destination if SoT already has one |
Default (no conventions): planning/roadmap.md (sequence-overlay / single-file map).
Honor existing: if planning/initiatives/ + planning/workstreams/ already exist, update
those instead of inventing a second SoT. Do not create hybrid sprawl for new projects unless the
user asks.
planning/conventions.md may name the dialect; absent → default file.
{A ∥ B}), or map-only /
sequencing-choice prose. Named NEXT without a planning shell is still consumable. Continue
auto-handoffs to swarm only for explicit ∥ / {wave} groups at the active head —
never invents a wave from ungrouped peers.planning/roadmap.md)# Roadmap: [horizon title]
Status: Active
Updated: [date]
## Destination
[One or two lines — what done looks like]
## Streams / order
Notation: `→` sequential · `∥` (or `||`) parallelizable · `{A ∥ B}` wave · `⚠ A ∥ B` collision watch
1. [claimable unit or stream name] — [one-line purpose]
2. …
Example order line: `Wave 0 → Wave 1 → (Wave 2 ∥ Wave 3) → Wave 4`
## NEXT
[resolvable unit | `{A ∥ B}` wave package | `map-only` | user sequencing choice — list options]
## Out of scope
- [ruled out for this horizon]
## Notes
[optional: depends-on, ⚠ collision watches, links to initiatives/workstreams]
| Token | Meaning | Continue behavior |
|---|---|---|
→ | Hard sequential dependency | Right side not claimable until left done |
∥ or ` | ` | |
{A ∥ B} | Named wave package | Preferred form for a swarm goal list |
⚠ A ∥ B | Soft collision (same layer / watch) | Not auto-launch; prefer sequential or caution |
map-only / sequencing choice | No single resolvable NEXT | hard-stop / surface choice — do not invent |
ASCII || is an accepted fallback for ∥ (U+2225). Informal // in chat means the same as ∥
but maps should use ∥ or ||.
Thin only: no acceptance criteria, no task lists, no status SoT (PM/session-state own status). Titles are mnemonics when PM owns the issue.
planning/initiatives/<name>.md — objective, priority order, guardrailsplanning/workstreams/<slug>.md — purpose, success, depends-on, link to item dir when startedNEXT or first incomplete workstream's unit@workflow:continue): explicit target → active swarm resume →
explicit ∥ / {wave} auto-handoff → in_progress → single NEXT → planned queue →
hard-stop.