You are helping the user refine a single roadmap milestone.
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:
-
Choose the milestone — determine whether the user wants to edit an
existing milestone or create a new one under
.spec-driven/roadmap/milestones/
.
-
Load milestone context — read:
.spec-driven/roadmap/INDEX.md
- the target milestone file when it already exists
- any nearby milestone files needed to preserve ordering or avoid overlap
- active and archived changes that the milestone already references or might
need to reference
-
Refine only one milestone at a time — help the user settle:
- the milestone
- derived
Use these standard section headings in the file:
-
Write the milestone file — create or update the milestone markdown file
and keep it focused on that milestone only.
-
Update roadmap index if needed — if the milestone is new, add it to
.spec-driven/roadmap/INDEX.md
in the correct sequence.
-
Enforce milestone status rules — if listed planned changes are not all
archived, the milestone is not complete. Do not add manual completion
overrides.
-
Validate roadmap size before finish — run:
node {{SKILL_DIR}}/scripts/spec-driven.js verify-roadmap
If validation reports that the milestone is too large, stop and tell the user
to split it instead of presenting the milestone as ready.
-
Report the result — summarize what changed in the milestone and identify
any candidate ideas that still need promotion into concrete changes.