gsd-complete-milestone

To archive a completed milestone, you need a valid v{{version}} milestone audit and complete phase summaries. The process archives project artifacts and updates planning documents like ROADMAP.md, REQUIREMENTS.md, and PROJECT.md to preserve the current state and enable next version planning.

Milestone archiving is the process of preserving completed project phases, audits, and documentation updates. You need it when a version is complete to ensure the milestone is auditable, generate git tags, and update the current project state for the next release.

After finishing a software release, you update ROADMAP.md and REQUIREMENTS.md by archiving the completed milestone artifacts. This workflow updates planning documents to reflect the newly archived state and prepares the project for next-milestone planning.

Yes, a valid v{{version}} milestone audit and complete phase summaries are required before archiving. These prerequisites ensure milestones are auditable and that project state updates are accurate before generating archived milestones with git tags.

Yes, generating git tags is part of the milestone archiving workflow. When you specify the target version and confirm the archive steps, the process creates archived milestones with git tags alongside updating your project planning documents.

Archiving milestones without complete phase summaries is not possible because the workflow requires a valid v{{version}} milestone audit. Missing these prerequisites prevents the proper updating of ROADMAP.md, REQUIREMENTS.md, and PROJECT.md and blocks the next-milestone preparation.