gsd-complete-milestone

Archive completed milestone roadmap and requirements with a versioned git tag.

Updated May 21, 2026
One-click install
npx skills add https://github.com/jedmamosto/m-and-ms --skill gsd-complete-milestone-jedmamosto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-complete-milestone
Source: https://github.com/jedmamosto/m-and-ms/tree/main/.agents/skills/gsd-complete-milestone
Command: npx skills add https://github.com/jedmamosto/m-and-ms --skill gsd-complete-milestone-jedmamosto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps teams reliably close out a completed milestone by archiving the shipped roadmap and requirements, updating the project documentation, and creating a version tag without losing historical context.

Core Features & Use Cases

  • Milestone completion workflow: Marks milestone {{version}} complete after verifying readiness and completion artifacts.
  • Archive roadmap and requirements: Creates versioned archives under .planning/milestones/ while keeping the working files fresh for the next milestone.
  • Documentation and git hygiene: Updates ROADMAP.md, REQUIREMENTS.md, PROJECT.md, STATE.md, and creates a v{{version}} annotated git tag.

Quick Start

Run the gsd-complete-milestone skill with the version you want to archive, for example gsd-complete-milestone with argument 2.0.

Frequently Asked Questions about gsd-complete-milestone

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I archive a completed project milestone and generate versioned documentation?

Milestone release governance requires verifying readiness, archiving roadmap and requirements records under `.planning/milestones/`, updating project state files, and creating an annotated git tag to ensure historical context is preserved.

What is the best way to manage release governance and update project state for the next iteration?

Milestone release governance involves consolidating completed work into historical artifacts, updating `ROADMAP.md` and `PROJECT.md`, deleting working requirements files, and applying a `v{{version}}` git tag to prepare for the next iteration.

How do I create a git tag for traceability after finishing a project milestone?

Creating a git tag for traceability involves committing updated project documentation and archived milestone files, then applying an annotated `v{{version}}` tag to mark the completed release in repository history.

Do I need phase summaries before archiving roadmap and requirements records?

Yes, phase summaries are required before archiving. The milestone completion workflow verifies that phase summaries exist before writing versioned roadmap and requirements archives and updating project state.

Why does completing a milestone require deleting the working `.planning/REQUIREMENTS.md` file?

Deleting the working `.planning/REQUIREMENTS.md` file clears completed requirements from the active planning cycle, keeping working files fresh for the next milestone while preserving historical context in versioned archives.

Can I use this milestone archive workflow to track project documentation changes across versions?

Yes, tracking project documentation changes across versions is supported because the workflow writes versioned `v{{version}}-ROADMAP.md` and `v{{version}}-REQUIREMENTS.md` archives, providing a historical record of each shipped milestone.