gsd-complete-milestone

Archive completed milestones by versioning roadmap and requirements files.

1|Updated May 24, 2026
One-click install
npx skills add https://github.com/tinner-deinno/innova-skills-lib --skill gsd-complete-milestone-tinner-deinno
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-complete-milestone
Source: https://github.com/tinner-deinno/innova-skills-lib/tree/main/core/gsd/gsd-complete-milestone
Command: npx skills add https://github.com/tinner-deinno/innova-skills-lib --skill gsd-complete-milestone-tinner-deinno

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents milestone chaos by ensuring a completed version is archived with preserved roadmap and requirements while the project state is updated for the next release.

Core Features & Use Cases

  • Milestone completion audit & readiness gating: checks for prior audit artifacts and ensures milestone phases have completed plans (SUMMARY files) before proceeding.
  • Versioned archival of planning artifacts: creates .planning/milestones/v{{version}}-ROADMAP.md and .planning/milestones/v{{version}}-REQUIREMENTS.md from current .planning/ROADMAP.md and .planning/REQUIREMENTS.md.
  • Project evolution & git tagging: updates .planning/PROJECT.md and .planning/STATE.md, collapses ROADMAP to a one-line entry, then commits and tags v{{version}} for traceability.
  • Use case: after finishing a multi-phase engineering initiative, finalize it by freezing its outcomes into versioned archive files so new work starts from a clean requirements baseline.

Quick Start

Ask the agent to complete the milestone by running the workflow for version "1.1" and archiving roadmap and requirements for that shipped 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 a completed project milestone and preserve its roadmap?

Milestone archival preserves your completed roadmap by generating versioned milestone files like `v{{version}}-ROADMAP.md` and `v{{version}}-REQUIREMENTS.md`. This freezes your project outcomes into historical records before starting new work.

What is git tagging for release governance and when do I need it?

Git tagging for release governance creates a traceable `v{{version}}` commit marker when a multi-phase development cycle finishes. You need it to enforce versioned historical records and maintain a clean requirements baseline for the next release.

How do I prepare planning artifacts for the next version after shipping?

Preparing planning artifacts involves collapsing your `ROADMAP.md` to a one-line entry and updating `PROJECT.md` and `STATE.md`. This clears the completed release baseline and configures the project state for the next development cycle.

Does milestone completion require phase summaries before archiving?

Milestone completion requires completed `SUMMARY.md` files for all project phases. This readiness gating checks for prior audit artifacts to ensure phases are finalized before proceeding with the archival workflow.

What is the best way to freeze requirements tracking for a shipped release?

Freezing requirements tracking for a shipped release is best handled by copying current `.planning/REQUIREMENTS.md` into a versioned archive. This approach maintains historical records while collapsing the active roadmap for future iterations.