gsd-complete-milestone

Archive milestone artifacts and update project files with a git tag.

Updated Feb 11, 2026
One-click install
npx skills add https://github.com/ArtRiv/game-topicos-especiais --skill gsd-complete-milestone-artriv
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-complete-milestone
Source: https://github.com/ArtRiv/game-topicos-especiais/tree/main/.github/skills/gsd-complete-milestone
Command: npx skills add https://github.com/ArtRiv/game-topicos-especiais --skill gsd-complete-milestone-artriv

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of finishing a project milestone without losing an auditable record of what shipped, why it shipped, and what must be done next.

Core Features & Use Cases

  • Milestone completion workflow: Runs a guided sequence to verify readiness, gather measurable stats, and extract key accomplishments from milestone phase artifacts.
  • Historical archiving: Creates versioned archive files for both the milestone roadmap and milestone requirements, preserving the context of the shipped version.
  • Project continuity updates: Evolves the project documentation (ROADMAP.md, REQUIREMENTS.md, PROJECT.md, STATE.md) and creates a git tag to mark the release point.
  • Use Case: After completing the planning and implementation of features for version 1.2, you can run this Skill to archive the milestone’s roadmap and requirements, collapse ROADMAP.md into a single-line entry, and tag the repository for traceability.

Quick Start

Provide the version you want to complete (for example, "1.2") and follow the prompts to archive the milestone, update project files, and create the git tag.

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 update the roadmap?

Archiving a completed project milestone involves verifying phase completion, generating versioned archive files under .planning/milestones/, and updating project documentation like ROADMAP.md and PROJECT.md to reflect the shipped version.

What is milestone archiving in release management and why is it needed?

Milestone archiving in release management is the process of finalizing a completed project phase by transforming its artifacts into versioned roadmap and requirements history, ensuring an auditable record of what shipped and why.

Does milestone completion automatically create a git tag for the released version?

Yes, milestone completion automatically creates a git tag for the specified version, marking the release point in the repository to ensure traceability and measurable shipped-version confirmation for project governance.

How do I reset requirements tracking for the next development milestone?

To reset requirements tracking for the next milestone, the completion workflow deletes and recreates REQUIREMENTS.md. This clears the previous milestone's requirements while preserving the old data in the versioned archive files under .planning/milestones/.

Can I finalize an iterative development milestone without losing phase documentation?

Yes, you can finalize an iterative development milestone without losing phase documentation. The workflow extracts key accomplishments and stats, generating versioned archive files for both the milestone roadmap and requirements to preserve context.

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

When a milestone is archived, PROJECT.md and STATE.md are evolved to reflect project continuity. This ensures the project documentation accurately tracks the current state after the milestone's roadmap and requirements are finalized and archived.