gsd-complete-milestone

Archives a completed milestone's roadmap and requirements and tags the repository.

4|1|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/lgwanai/openforce --skill gsd-complete-milestone-lgwanai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-complete-milestone
Source: https://github.com/lgwanai/openforce/tree/main/skills/gsd-complete-milestone
Command: npx skills add https://github.com/lgwanai/openforce --skill gsd-complete-milestone-lgwanai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents stalled releases by turning a completed milestone into an immutable archive, updating planning artifacts for the next cycle.

Core Features & Use Cases

  • Milestone readiness verification: Checks whether milestone phases have completed plans (by verifying SUMMARY.md presence) before proceeding.
  • Milestone statistics and accomplishments extraction: Counts phases/plans/tasks, analyzes git range and file changes, and extracts key accomplishments from phase summaries.
  • Archival and planning evolution: Creates archived ROADMAP and REQUIREMENTS snapshots under .planning/milestones/, updates ROADMAP.md and PROJECT.md, then prepares the repository for the next milestone with a fresh requirements state and a git tag.

Quick Start

Run gsd-complete-milestone with the version you just finished, for example: openforce /gsd:complete-milestone 1.1.

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 shipped milestone and prepare the repository for the next release?

To archive a shipped milestone, you can verify phase completion via SUMMARY.md files, generate milestone archive snapshots under .planning/milestones/, update ROADMAP.md and PROJECT.md, and create a version git tag.

What is milestone readiness verification in project release management?

Milestone readiness verification is the process of checking whether milestone phases have completed plans by validating the presence of SUMMARY.md files before proceeding with release archival.

How do I generate milestone statistics and extract accomplishments for a roadmap archive?

You can generate milestone statistics by counting phases, plans, and tasks, analyzing the git range and file changes, and extracting key accomplishments from phase summaries into historical archive files.

Can I automate git tagging and roadmap updates when a versioned milestone is completed?

Yes, you can automate git tagging and roadmap updates by running a workflow that validates milestone audit readiness, persists records into historical files, updates current planning state, and applies a version git tag.

What happens to current planning artifacts when completing a milestone?

When completing a milestone, current planning artifacts are evolved by creating archived ROADMAP and REQUIREMENTS snapshots and updating PROJECT.md to prepare the repository for the next milestone cycle.

Why does milestone archival require checking for SUMMARY.md files?

Milestone archival requires checking for SUMMARY.md files to verify that all milestone phases have valid completion plans, preventing stalled releases by ensuring audit readiness before archiving.