You are helping the user synchronize
with the current
change history.
The
directory must exist at the
project root. Before
proceeding, verify:
If this fails, the project is not initialized. Run
first.
If
is missing, repair the scaffold first:
-
Read roadmap state first — before changing anything, read:
.spec-driven/roadmap/INDEX.md
- every milestone file listed in the roadmap index
- run
node {{SKILL_DIR}}/scripts/spec-driven.js roadmap-status
- inspect the returned milestone and planned change state summary
-
Compare roadmap to repository reality — use the
output
as the source of deterministic comparison. For each milestone in scope,
identify:
- planned changes that are archived
- planned changes that still exist as active work
- planned changes that are missing or renamed
- milestone statuses that no longer match the derived status
- any ambiguity the script cannot resolve, such as likely renames or roadmap
prose that still needs human judgment
-
Update roadmap files — reconcile milestone status and listed change state
based on the repository evidence you found.
-
Preserve roadmap rules — during sync:
- do not mark a milestone complete unless every listed planned change is
archived
- keep the roadmap as planning state, not an implementation log
-
Validate roadmap size before finish — run:
node {{SKILL_DIR}}/scripts/spec-driven.js verify-roadmap
If validation reports that any milestone is too large, stop and tell the user
to split it instead of presenting roadmap sync as complete.
-
Report the sync result — summarize:
- milestones updated
- planned changes whose state changed
- missing or ambiguous references that still need human cleanup