# Gsd Complete Milestone

Use when every phase in a milestone is complete and the user wants to archive it, tag...

- Repository: https://github.com/coco-research/coco (797 stars)
- Category: Engineering
- License: see repository
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add coco-research/coco --skill gsd-complete-milestone -g -a claude-code -y`
Codex: `npx skills add coco-research/coco --skill gsd-complete-milestone -g -a codex -y`
Cursor: `npx skills add coco-research/coco --skill gsd-complete-milestone -g -a cursor -y`
Gemini CLI: `npx skills add coco-research/coco --skill gsd-complete-milestone -g -a gemini-cli -y`

## Description

Use when every phase in a milestone is complete and the user wants to archive it, tag the release, and start the next version. Archives roadmap and requirements to .planning/milestones/, updates PROJECT.md, then tags the version.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

<objective>
Mark milestone $ARGUMENTS complete, archive to milestones/, and update ROADMAP.md and REQUIREMENTS.md.

Purpose: Create historical record of shipped version, archive milestone artifacts (roadmap + requirements), and prepare for next milestone.
Output: Milestone archived (roadmap + requirements), PROJECT.md evolved, git tagged.
</objective>

<execution_context>
**Load these files NOW (before proceeding):**

- @$HOME/.claude/get-shit-done/workflows/complete-milestone.md (main workflow)
- @$HOME/.claude/get-shit-done/templates/milestone-archive.md (archive template)
  </execution_context>

<context>
**Project files:**
- `.planning/ROADMAP.md`
- `.planning/REQUIREMENTS.md`
- `.planning/STATE.md`
- `.planning/PROJECT.md`

**User input:**

- Version: $ARGUMENTS (e.g., "1.0", "1.1", "2.0")
  </context>

<process>

**Follow complete-milestone.md workflow:**

0. **Check for audit:**

   - Look for `.planning/v$ARGUMENTS-MILESTONE-AUDIT.md`
   - If missing or stale: recommend `/gsd-audit-milestone` first
   - If audit status is `gaps_found`: recommend `/gsd-plan-milestone-gaps` first
   - If audit status is `passed`: proceed to step 1

   ```markdown
   ## Pre-flight Check

   {If no v$ARGUMENTS-MILESTONE-AUDIT.md:}
   ⚠ No milestone audit found. Run `/gsd-audit-milestone` first to verify
   requirements coverage, cross-phase integration, and E2E flows.

   {If audit has gaps:}
   ⚠ Milestone audit found gaps. Run `/gsd-plan-milestone-gaps` to create
   phases that close the gaps, or proceed anyway to accept as tech debt.

   {If audit passed:}
   ✓ Milestone audit passed. Proceeding with completion.
   ```

1. **Verify readiness:**

   - Check all phases in milestone have completed plans (SUMMARY.md exists)
   - Present milestone scope and stats
   - Wait for confirmation

2. **Gather stats:**

   - Count phases, plans, tasks
   - Calculate git range, file changes, LOC
   - Extract timeline from git log
   - Present summary, confirm

The rest: https://github.com/coco-research/coco/blob/HEAD/systems/gsd/skills/gsd-complete-milestone/SKILL.md