gsd-complete-milestone

Archive completed milestones with versioned roadmap and requirements history.

4|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/electroheadfx/efx-mux --skill gsd-complete-milestone-electroheadfx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-complete-milestone
Source: https://github.com/electroheadfx/efx-mux/tree/main/.codex/skills/gsd-complete-milestone
Command: npx skills add https://github.com/electroheadfx/efx-mux --skill gsd-complete-milestone-electroheadfx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you formally close out a completed milestone by archiving roadmap and requirements artifacts, updating project state, and preparing the next version without losing historical context.

Core Features & Use Cases

  • Milestone verification: Checks that the milestone has the required audit and completed phase summaries before archiving.
  • Artifact archival: Creates versioned roadmap and requirements archives in the milestones folder and collapses the live planning files into concise summaries.
  • Project rollover: Updates PROJECT.md, records the shipped state, and prepares the repository for the next milestone.
  • Use case: After shipping version 1.2, use this Skill to preserve the milestone record, keep planning docs tidy, and move the project forward with a clean baseline.

Quick Start

Use the gsd-complete-milestone skill to archive version 1.2 and prepare the project for the next milestone.

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 milestone and preserve roadmap history in release management?

Archiving a completed milestone involves preserving roadmap and requirements history by creating versioned archives in the milestones folder, then collapsing live planning files into concise summaries. This ensures historical context is kept while updating project state for the next cycle.

What is the best way to prepare a project for the next milestone after shipping a release?

Preparing for the next milestone requires updating PROJECT.md to record the shipped state and rolling over project artifacts. This formal closure creates a clean baseline, keeping planning documentation tidy and ready for upcoming development phases.

Do I need git history review and phase summaries before archiving a project milestone?

Yes, archiving a milestone requires git history review and completed phase summaries for audit verification. The process validates these required milestone-specific documentation artifacts before proceeding with versioned archival of planning files.

Can I use this milestone archival process to collapse live planning files like ROADMAP.md and REQUIREMENTS.md?

Yes, the milestone archival process specifically updates ROADMAP.md and REQUIREMENTS.md by collapsing them into concise summaries. It preserves the detailed history in versioned archives within the milestones folder while resetting the live documents.

Why does milestone archival require audit verification before updating the project state?

Audit verification is required during milestone archival to ensure all completed phase summaries and documentation are valid before project state changes. This controlled update prevents losing critical historical context when transitioning between release management cycles.