ferrox-complete-milestone

Archiving a completed milestone involves validating readiness through phase summaries, creating versioned archives of your roadmap and requirements, then collapsing active planning files into concise current-state references to prepare for the next version.

Before archiving a shipped release, you must check milestone audits and verify that completed phase summaries exist in the SUMMARY.md records. These readiness checks ensure the milestone is fully validated before creating archives and git tags.

Release prep for a milestone involves updating project status, preparing the next milestone context, and applying git commit hygiene. After validating readiness and creating versioned archives, you prepare the git tag and commit to finalize the shipped version.

After a version ships, create versioned roadmap and requirements archives to preserve history, then collapse the active planning files into concise current-state references. This approach maintains the historical record while resetting the workspace for the next planning cycle.

Milestone archival works for release management workflows without external dependencies. It handles phase verification, archive creation, and git tag preparation internally by checking milestone audits and SUMMARY.md phase records within your project state.

You should not use a milestone archival process when phase summaries are incomplete or milestone audits fail. If readiness checks fail, collapsing active planning files and creating versioned archives prematurely would lose the context needed to properly finish the shipped version.