gsd-complete-milestone

To archive completed project milestones and prepare for the next version, you can invoke a workflow that archives roadmap and requirements artifacts, updates PROJECT.md, and tags the release in git. This preserves delivery history and streamlines planning.

The best way to preserve delivery history is archiving milestone ROADMAP.md and REQUIREMENTS.md files into versioned records under .planning/milestones/. This ensures past project artifacts are systematically saved before transitioning to the next development phase.

Milestone archiving works by generating versioned records of roadmaps and requirements, updating PROJECT.md with current state and next goals, then creating a git tag for the shipped version and committing all changes to the repository.

Yes, you need a versioned project structure that manages milestones, roadmaps, and requirements. The archiving and tagging process applies specifically to projects that track delivery through structured versioning and milestone planning.

Yes, you can automate updating PROJECT.md with the current state and next milestone goals, while simultaneously creating a git tag for the shipped version. This handles audit, planning, archiving, and tagging processes in one workflow.

This milestone archiving process is limited to versioned projects that actively manage milestones, roadmaps, and requirements. Projects lacking structured planning files like ROADMAP.md or REQUIREMENTS.md cannot utilize this archiving workflow.