gsd-complete-milestone

Archive completed milestone artifacts and update planning documents with git tagging.

8|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/D0NMEGA/donnyclaude --skill gsd-complete-milestone-d0nmega
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-complete-milestone
Source: https://github.com/D0NMEGA/donnyclaude/tree/main/packages/skills/gsd-complete-milestone
Command: npx skills add https://github.com/D0NMEGA/donnyclaude --skill gsd-complete-milestone-d0nmega

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive completed milestone artifacts and update planning documents to preserve a historical record.

Core Features & Use Cases

  • Archive shipped milestones to the milestones folder, update ROADMAP.md and REQUIREMENTS.md, and evolve PROJECT.md with current state.
  • Prepare the next milestone by initializing a fresh STATE and ROADMAP skeleton, and tag the git repository for traceability.
  • Provide a deterministic, auditable workflow for archival and next-milestone preparation that can be rerun reliably.

Quick Start

Run the complete milestone workflow for the target version to archive and prep 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 completed project milestones and update my roadmap?

To archive completed milestones, you move milestone artifacts to a milestones folder, update ROADMAP.md and REQUIREMENTS.md, and evolve PROJECT.md with the current state to preserve a historical record.

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

Preparing the next milestone involves initializing a fresh STATE and ROADMAP skeleton, then tagging the git repository to ensure traceability and reproducibility for the upcoming development cycle.

How does git tagging work with milestone archiving to ensure traceability?

Git tagging during milestone archiving marks the specific repository state when a version shipped, linking the archived ROADMAP and REQUIREMENTS documents to an immutable commit for reproducible audits.

Can I use this milestone workflow for versioned projects without existing planning documents?

No, this workflow applies to versioned projects that already require ROADMAP and REQUIREMENTS archiving, as it performs audit checks and status verification against existing planning documents before archiving.

What happens to PROJECT.md state when a milestone is archived?

When archiving a milestone, PROJECT.md is evolved with the current state to reflect the completed work, ensuring the primary project file accurately tracks historical progress and next-milestone preparation.

Why does milestone archiving require audit checks and status verification?

Audit checks and status verification enforce a deterministic, auditable workflow that confirms milestone completion before archiving, ensuring the archival process can be rerun reliably without losing traceability.