gsd-complete-milestone

Archive completed milestones and update project documentation with version tagging.

Updated Jan 25, 2026
One-click install
npx skills add https://github.com/MINT-IA/MINT --skill gsd-complete-milestone-mint-ia
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-complete-milestone
Source: https://github.com/MINT-IA/MINT/tree/main/.claude/skills/gsd-complete-milestone
Command: npx skills add https://github.com/MINT-IA/MINT --skill gsd-complete-milestone-mint-ia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archiving completed software milestones and preparing the next version by updating ROADMAP.md and REQUIREMENTS.md while preserving a structured historical record.

Core Features & Use Cases

  • Milestone archival: create v{{version}}-ROADMAP.md and v{{version}}-REQUIREMENTS.md and archive artifacts from the milestone.
  • Documentation updates: update PROJECT.md with current state and next milestone goals.
  • Version tagging: create a git tag v{{version}} for the milestone release; ensure safe commits and prompts for pushing.
  • Compliance with workflow: enforce pre-flight audit checks and ensure all phases have SUMMARY.md.

Quick Start

Run the complete milestone archive workflow for the specified version.

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 completed project milestones and update project documentation for the next version?

Archive completed project milestones by automating the creation of v{{version}}-ROADMAP.md and v{{version}}-REQUIREMENTS.md files, updating PROJECT.md with the next goals, and managing git version tagging for the release.

What is the best way to automate git tagging and roadmap creation during a milestone archival workflow?

Automate milestone archival by enforcing pre-flight audit checks, generating structured ROADMAP.md and REQUIREMENTS.md artifacts, and creating a git tag v{{version}} with safe commit prompts for the release.

Do I need SUMMARY.md files for all phases before running a complete milestone archival workflow?

Yes, a complete milestone archival workflow enforces compliance by requiring pre-flight audit checks and ensuring all project phases have SUMMARY.md files before proceeding to version tagging.

How does milestone archival preserve historical records while preparing requirements for the next version?

Milestone archival preserves historical records by creating dedicated v{{version}}-ROADMAP.md and v{{version}}-REQUIREMENTS.md files, while updating PROJECT.md to reflect the current state and define the next milestone goals.

Can I use this milestone archival process to enforce requirements alignment and audit checks before version tagging?

Yes, the milestone archival process applies to end-to-end workflows by enforcing pre-flight audit checks, ensuring requirements alignment, and managing git version tagging safely before prompting to push.