gsd-complete-milestone

Name: gsd-complete-milestone
Availability: InStock
Author: rkz91

Archive milestone roadmaps and requirements, update PROJECT.md, and tag releases in git.

264|11|Updated Apr 25, 2026

Search Tags:#versioning #roadmap #archiving #project-management #version-control #milestone

Ready to run

npx skills add https://github.com/rkz91/coco --skill gsd-complete-milestone-rkz91

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gsd-complete-milestone
Source: https://github.com/rkz91/coco/tree/main/systems/gsd/skills/gsd-complete-milestone
Command: npx skills add https://github.com/rkz91/coco --skill gsd-complete-milestone-rkz91

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive completed milestones and prepare for the next version to preserve delivery history and streamline planning.

Core Features & Use Cases

Archive milestone ROADMAP.md and REQUIREMENTS.md into versioned records under .planning/milestones/.
Update PROJECT.md with the current state and the goals for the next milestone.
Create a git tag for the shipped version and commit all changes to the repository.

Quick Start

Invoke the gsd-complete-milestone workflow with the target version to archive the milestone and prepare the next 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 prepare for the next version?▼

To archive completed project milestones and prepare for the next version, you can invoke a workflow that archives roadmap and requirements artifacts, updates PROJECT.md, and tags the release in git. This preserves delivery history and streamlines planning.

What is the best way to preserve delivery history when finishing a project milestone?▼

The best way to preserve delivery history is archiving milestone ROADMAP.md and REQUIREMENTS.md files into versioned records under .planning/milestones/. This ensures past project artifacts are systematically saved before transitioning to the next development phase.

How does milestone archiving work with git tags and PROJECT.md updates?▼

Milestone archiving works by generating versioned records of roadmaps and requirements, updating PROJECT.md with current state and next goals, then creating a git tag for the shipped version and committing all changes to the repository.

Do I need a versioned project structure to manage milestone roadmaps and requirements?▼

Yes, you need a versioned project structure that manages milestones, roadmaps, and requirements. The archiving and tagging process applies specifically to projects that track delivery through structured versioning and milestone planning.

Can I automate updating PROJECT.md and tagging releases when a milestone is done?▼

Yes, you can automate updating PROJECT.md with the current state and next milestone goals, while simultaneously creating a git tag for the shipped version. This handles audit, planning, archiving, and tagging processes in one workflow.

What limitations exist when archiving milestones for versioned projects?▼

This milestone archiving process is limited to versioned projects that actively manage milestones, roadmaps, and requirements. Projects lacking structured planning files like ROADMAP.md or REQUIREMENTS.md cannot utilize this archiving workflow.