Managing the plan
Changing scope mid-milestone: adding objectives, auditing, archiving, and fixing drift.
| Command | Arguments | What it does |
|---|---|---|
/devflow:objective | <add|remove> [args...] | Add or remove an objective from the current milestone roadmap. |
/devflow:milestonetype it yourself | <new|audit|complete|gaps> [args...] | Manage milestones: start a new one, audit a finished one, complete it, or plan gap-closure objectives. |
/devflow:list-objective-assumptionstype it yourself | [objective] | See what Claude plans to do for an objective before it starts, so you can course-correct early. |
/devflow:sync-roadmap | [--dry-run] [--interactive] [--raw] | Reconcile ROADMAP.md checkbox state against on-disk SUMMARY.md presence. Default: silently corrects drift; --dry-run previews; --interactive prompts per change. |
/devflow:cleanuptype it yourself | — | Archive old objective directories from completed milestones to reduce clutter. |
Most of these are user-typed only
/devflow:objective, /devflow:milestone and /devflow:cleanup all carry
disable-model-invocation: true. Claude cannot fire them — you type them. They
mutate planning state in ways that are tedious to undo./devflow:objective
/devflow:objective add "add webhook retry with exponential backoff"
/devflow:objective remove 7
Adds or removes an objective in the current milestone’s roadmap.
remove renumbers everything above it
remove cascade-renumbers every objective above the one you removed. Objective 8
becomes 7, 9 becomes 8, and so on — including their directory names. If you have
notes, branches or issues referencing objective numbers, they will be wrong
afterwards.
add also slugifies the whole description into the directory name, so keep
descriptions short or you get a very long path.
The insert subcommand (decimal objectives like 4.1) was removed in v1.2. Use
add instead.
/devflow:milestone
/devflow:milestone new
/devflow:milestone audit
/devflow:milestone gaps
/devflow:milestone complete
new opens a milestone: fresh requirements scoping and a fresh roadmap inside
an existing project.
audit checks that every v1 requirement was genuinely delivered — not that
every objective is ticked, but that the requirements those objectives existed to
satisfy are actually met. It reports gaps.
gaps turns audit findings into gap-closure objectives you can plan and build.
complete archives the milestone to MILESTONES.md and
.planning/milestones/, then opens the next.
/devflow:list-objective-assumptions
/devflow:list-objective-assumptions 5
Shows what Claude intends to do for an objective without creating any files.
Read it before planning; if the intent is wrong, run /devflow:discuss-objective
and correct it there. Far cheaper than discovering the misunderstanding after a
build.
/devflow:sync-roadmap
/devflow:sync-roadmap --dry-run
/devflow:sync-roadmap
/devflow:sync-roadmap --interactive
Reconciles ROADMAP.md checkbox state against on-disk SUMMARY.md presence.
Default behaviour silently corrects drift; --dry-run previews; --interactive
prompts per change.
Run it when work happened outside DevFlow, or when the roadmap and reality disagree about what’s done.
/devflow:cleanup
/devflow:cleanup
Archives objective directories from completed milestones to reduce clutter. Only touches completed work, and only when you explicitly ask.