gsd-complete-milestone

Archive completed milestones by compiling roadmap and requirements into versioned git artifacts.

1|Updated Sep 6, 2015

Search Tags:#release management #project planning #git tagging #requirements tracking #roadmap update #milestone archival

Ready to run

npx skills add https://github.com/deerawan/dotfiles --skill gsd-complete-milestone-deerawan

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of leaving version milestones unarchived and untracked, so roadmap and requirements drift instead of preserving a reliable historical record.

Core Features & Use Cases

Milestone completion workflow: runs audit/verification gates, confirms milestone phase completion, and gathers stats from git history.
Archive shipped scope: generates versioned archived roadmap and requirements files and updates the main planning docs into a “current state” summary.
Project bookkeeping: evolves PROJECT.md, updates ROADMAP.md to a one-line entry with a link, commits changes, and creates a signed/annotated git tag for the shipped version.

Quick Start

Run the gsd-complete-milestone skill and provide the target milestone version (for example, 1.0) to archive the completed milestone, update planning files, and tag the release in git.

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 tag the release in git?▼

To archive a completed milestone, this skill compiles roadmap and requirements into versioned historical artifacts, updates PROJECT.md and ROADMAP.md, commits the changes, and creates an annotated git tag for the specified shipped version.

What happens to roadmap and requirements files when a version milestone is marked complete?▼

When a version milestone is marked complete, roadmap and requirements files are generated as versioned archived records. The main planning docs are then updated into a current state summary with a one-line roadmap entry linking to the archive.

Do I need to manually verify milestone phase completion before archiving a release?▼

Manual verification is not strictly required beforehand because the milestone completion workflow runs audit and verification gates, confirms phase completion, and gathers statistics from git history as part of the archival process.

What's the best way to preserve historical release management records before starting the next milestone?▼

The best way to preserve historical records is to run a complete-milestone workflow that generates archived roadmap and requirements files, preventing planning drift by maintaining a reliable, versioned historical record before starting the next milestone.

How does project bookkeeping work when finalizing a shipped version?▼

Project bookkeeping for a shipped version evolves PROJECT.md, updates ROADMAP.md to a single entry with a link, commits all planning file changes, and creates a signed or annotated git tag for the provided version.

Can I use this milestone archival process without a git repository?▼

No, this process requires a git repository because it commits planning file changes and creates a signed or annotated git tag for the shipped version as part of the milestone completion workflow.