gsd-complete-milestone

Archive milestone ROADMAP and REQUIREMENTS docs into versioned artifacts.

Updated Aug 15, 2025
One-click install
npx skills add https://github.com/gesmith0606/nfl_data_engineering --skill gsd-complete-milestone-gesmith0606
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-complete-milestone
Source: https://github.com/gesmith0606/nfl_data_engineering/tree/main/.claude/skills/gsd-complete-milestone
Command: npx skills add https://github.com/gesmith0606/nfl_data_engineering --skill gsd-complete-milestone-gesmith0606

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive completed milestone versions and standardize artifact retention, ensuring a reliable historical record of shipped changes and a clean handoff for the next release.

Core Features & Use Cases

  • Archive milestone ROADMAP.md and REQUIREMENTS.md into versioned artifacts under .planning/milestones/v{{version}}-ROADMAP.md and .planning/milestones/v{{version}}-REQUIREMENTS.md.
  • Update PROJECT.md to reflect the current state, ship status, and the "Next Milestone Goals" section for planning continuity.
  • Create a one-line summary entry in ROADMAP.md that links to the archived milestone to maintain a concise historical index.

Quick Start

Run the complete-milestone workflow with the target version to archive artifacts, update project state, and tag the release.

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 retain roadmap documentation?▼

To archive project milestones, you copy completed ROADMAP.md and REQUIREMENTS.md files into versioned artifacts under .planning/milestones, preserving historical context and ensuring traceability for shipped releases.

What is the best way to maintain a historical index of shipped versions in project management docs?▼

Maintaining a historical index involves creating a one-line summary entry in your ROADMAP.md that links directly to the archived milestone artifacts, keeping a concise record of all past releases.

How do I update PROJECT.md to reflect a shipped milestone and prep for the next release?▼

Updating PROJECT.md involves modifying the current state and ship status sections, while populating the Next Milestone Goals section to ensure planning continuity for the upcoming development cycle.

Does archiving a milestone version automatically tag the repository?▼

Yes, the milestone archiving workflow tags the repository as part of its completion process, linking the release tag to the standardized artifacts stored under .planning/milestones.

When should I not use automated milestone archiving for project documentation?▼

You should avoid automated milestone archiving if your project lacks structured ROADMAP.md or REQUIREMENTS.md files, since the workflow depends on these specific documents to extract and preserve historical context.

Can I standardize artifact retention across multiple project planning documents?▼

Yes, you can standardize artifact retention by applying the archiving workflow across ROADMAP, REQUIREMENTS, and PROJECT docs, creating milestone-specific archives that ensure a clean handoff for the next version.