gsd-complete-milestone

Milestone archival is automated by auditing readiness, generating ROADMAP and REQUIREMENTS summaries under .planning/milestones, updating PROJECT.md, and creating a git tag. This workflow ensures consistent release records and preps the next milestone with minimal manual toil.

Updating PROJECT.md involves reflecting the current milestone state and documenting the planned next milestone. The archival workflow modifies PROJECT.md alongside ROADMAP.md and REQUIREMENTS.md to maintain accurate project tracking after a release.

Creating a git tag during milestone archival happens automatically by tagging the release as v{{version}}. The workflow commits updated ROADMAP.md, REQUIREMENTS.md, and PROJECT.md changes before applying the version tag.

Archiving ROADMAP and REQUIREMENTS files is needed when completing a software milestone release that requires structured records. The process audits milestone readiness, drafts archived versions under .planning/milestones, and prepares artifacts for the next development cycle.

Yes, this milestone archival workflow operates without external dependencies. It independently audits milestone readiness, generates archival artifacts, updates project documentation, and tags releases within your existing version control environment.

Preparing for the next milestone after a release involves archiving current ROADMAP and REQUIREMENTS documents, updating PROJECT.md with the new planned milestone, and tagging the completed release in version control to establish a clean baseline.