gsd-complete-milestone

Automate milestone closure, archival, reporting, and git tagging in GSD workflows.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/optivent/gsd-kimi-cli --skill gsd-complete-milestone
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-complete-milestone
Source: https://github.com/optivent/gsd-kimi-cli/tree/main/skills/gsd-complete-milestone
Command: npx skills add https://github.com/optivent/gsd-kimi-cli --skill gsd-complete-milestone

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically manage milestone completion by validating all phases, archiving related work, and updating project state to reflect delivery.

Core Features & Use Cases

  • Verify all phases in a milestone are complete and all verifications pass.
  • Archive milestone work to the planning archive, create a milestone summary, and tag the git commit.
  • Generate a Milestone Complete report with delivered phases, key deliverables, and metrics, and update STATE.md.

Quick Start

Run the milestone completion command to close a milestone and trigger archival, reporting, and state updates.

Frequently Asked Questions about gsd-complete-milestone

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate project milestone closure and archive completed work?

You can automate milestone closure by validating all phases are complete and verifications pass, archiving work to the planning archive, and updating the project state to reflect delivery. This process also generates a milestone summary and tags git commits.

What is included in a Milestone Complete report for project management?

A Milestone Complete report includes delivered phases, key deliverables, and metrics. It serves to document the milestone completion while simultaneously updating STATE.md to reflect the new project lifecycle state.

How do I update STATE.md and tag git commits when a milestone is complete?

Updating STATE.md and tagging git commits happens automatically during the milestone closure workflow. Once all phases verify successfully, the process applies lifecycle state updates to the file and tags the corresponding git commit.

Does milestone closure work if some phase verifications have not passed?

Milestone closure requires all phases to be complete and all verifications to pass before proceeding. If verifications fail, the workflow prevents archival, reporting, and state updates until the issues are resolved.

What's the best way to verify all phases are complete before archiving a milestone?

The best way to verify phases before archiving is to run an automated milestone completion command that checks if all phases are complete and verifications pass. This ensures only fully delivered milestones are archived and reported.