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.
- @{{PLATFORM_ROOT}}/get-shit-done/workflows/complete-milestone.md (main workflow)
- @{{PLATFORM_ROOT}}/get-shit-done/templates/milestone-archive.md (archive template)
User input:
- Version: {{version}} (e.g., "1.0", "1.1", "2.0")
Follow complete-milestone.md workflow:
Check for audit:
- Look for
.planning/v{{version}}-MILESTONE-AUDIT.md
- If missing or stale: recommend
{{COMMAND_PREFIX}}audit-milestone first
- If audit status is
gaps_found: recommend {{COMMAND_PREFIX}}plan-milestone-gaps first
- If audit status is
passed: proceed to step 1
## Pre-flight Check
{If no v{{version}}-MILESTONE-AUDIT.md:}
⚠ No milestone audit found. Run `{{COMMAND_PREFIX}}audit-milestone` first to verify
requirements coverage, cross-phase integration, and E2E flows.
{If audit has gaps:}
⚠ Milestone audit found gaps. Run `{{COMMAND_PREFIX}}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.
Verify readiness:
- Check all phases in milestone have completed plans (SUMMARY.md exists)
- Present milestone scope and stats
- Wait for confirmation
Gather stats:
- Count phases, plans, tasks
- Calculate git range, file changes, LOC
- Extract timeline from git log
- Present summary, confirm
Extract accomplishments:
- Read all phase SUMMARY.md files in milestone range
- Extract 4-6 key accomplishments
- Present for approval
Archive milestone:
- Create
.planning/milestones/v{{version}}-ROADMAP.md
- Extract full phase details from ROADMAP.md
- Fill milestone-archive.md template
- Update ROADMAP.md to one-line summary with link
Archive requirements:
- Create
.planning/milestones/v{{version}}-REQUIREMENTS.md
- Mark all v1 requirements as complete (checkboxes checked)
- Note requirement outcomes (validated, adjusted, dropped)
- Delete
.planning/REQUIREMENTS.md (fresh one created for next milestone)
Update PROJECT.md:
- Add "Current State" section with shipped version
- Add "Next Milestone Goals" section
- Archive previous content in
<details> (if v1.1+)
Commit and tag:
- Stage: MILESTONES.md, PROJECT.md, ROADMAP.md, STATE.md, archive files
- Commit:
chore: archive v{{version}} milestone
- Tag:
git tag -a v{{version}} -m "[milestone summary]"
- Ask about pushing tag
Offer next steps:
{{COMMAND_PREFIX}}new-milestone — start next milestone (questioning → research → requirements → roadmap)
- Milestone archived to
.planning/milestones/v{{version}}-ROADMAP.md
- Requirements archived to
.planning/milestones/v{{version}}-REQUIREMENTS.md
.planning/REQUIREMENTS.md deleted (fresh for next milestone)
- ROADMAP.md collapsed to one-line entry
- PROJECT.md updated with current state
- Git tag v{{version}} created
- Commit successful
- User knows next steps (including need for fresh requirements)
- Load workflow first: Read complete-milestone.md before executing
- Verify completion: All phases must have SUMMARY.md files
- User confirmation: Wait for approval at verification gates
- Archive before deleting: Always create archive files before updating/deleting originals
- One-line summary: Collapsed milestone in ROADMAP.md should be single line with link
- Context efficiency: Archive keeps ROADMAP.md and REQUIREMENTS.md constant size per milestone
- Fresh requirements: Next milestone starts with
{{COMMAND_PREFIX}}new-milestone which includes requirements definition
1---
2name: gsd-complete-milestone
3description: Archive completed milestone and prepare for next version
4argument-hint: <version>
5allowed-tools: Read, Write, Bash
6metadata:
7 source: https://skillmd.com/skills/shoootyou/gsd-complete-milestone
8---
9
10<objective>
11Mark milestone {{version}} complete, archive to milestones/, and update ROADMAP.md and REQUIREMENTS.md.
12
13Purpose: Create historical record of shipped version, archive milestone artifacts (roadmap + requirements), and prepare for next milestone.
14Output: Milestone archived (roadmap + requirements), PROJECT.md evolved, git tagged.
15</objective>
16
17<execution_context>
18**Load these files NOW (before proceeding):**
19
20- @{{PLATFORM_ROOT}}/get-shit-done/workflows/complete-milestone.md (main workflow)
21- @{{PLATFORM_ROOT}}/get-shit-done/templates/milestone-archive.md (archive template)
22 </execution_context>
23
24<context>
25**Project files:**
26- `.planning/ROADMAP.md`
27- `.planning/REQUIREMENTS.md`
28- `.planning/STATE.md`
29- `.planning/PROJECT.md`
30
31**User input:**
32
33- Version: {{version}} (e.g., "1.0", "1.1", "2.0")
34 </context>
35
36<process>
37
38**Follow complete-milestone.md workflow:**
39
400. **Check for audit:**
41
42 - Look for `.planning/v{{version}}-MILESTONE-AUDIT.md`
43 - If missing or stale: recommend `{{COMMAND_PREFIX}}audit-milestone` first
44 - If audit status is `gaps_found`: recommend `{{COMMAND_PREFIX}}plan-milestone-gaps` first
45 - If audit status is `passed`: proceed to step 1
46
47 ```markdown
48 ## Pre-flight Check
49
50 {If no v{{version}}-MILESTONE-AUDIT.md:}
51 ⚠ No milestone audit found. Run `{{COMMAND_PREFIX}}audit-milestone` first to verify
52 requirements coverage, cross-phase integration, and E2E flows.
53
54 {If audit has gaps:}
55 ⚠ Milestone audit found gaps. Run `{{COMMAND_PREFIX}}plan-milestone-gaps` to create
56 phases that close the gaps, or proceed anyway to accept as tech debt.
57
58 {If audit passed:}
59 ✓ Milestone audit passed. Proceeding with completion.
60 ```
61
621. **Verify readiness:**
63
64 - Check all phases in milestone have completed plans (SUMMARY.md exists)
65 - Present milestone scope and stats
66 - Wait for confirmation
67
682. **Gather stats:**
69
70 - Count phases, plans, tasks
71 - Calculate git range, file changes, LOC
72 - Extract timeline from git log
73 - Present summary, confirm
74
753. **Extract accomplishments:**
76
77 - Read all phase SUMMARY.md files in milestone range
78 - Extract 4-6 key accomplishments
79 - Present for approval
80
814. **Archive milestone:**
82
83 - Create `.planning/milestones/v{{version}}-ROADMAP.md`
84 - Extract full phase details from ROADMAP.md
85 - Fill milestone-archive.md template
86 - Update ROADMAP.md to one-line summary with link
87
885. **Archive requirements:**
89
90 - Create `.planning/milestones/v{{version}}-REQUIREMENTS.md`
91 - Mark all v1 requirements as complete (checkboxes checked)
92 - Note requirement outcomes (validated, adjusted, dropped)
93 - Delete `.planning/REQUIREMENTS.md` (fresh one created for next milestone)
94
956. **Update PROJECT.md:**
96
97 - Add "Current State" section with shipped version
98 - Add "Next Milestone Goals" section
99 - Archive previous content in `<details>` (if v1.1+)
100
1017. **Commit and tag:**
102
103 - Stage: MILESTONES.md, PROJECT.md, ROADMAP.md, STATE.md, archive files
104 - Commit: `chore: archive v{{version}} milestone`
105 - Tag: `git tag -a v{{version}} -m "[milestone summary]"`
106 - Ask about pushing tag
107
1088. **Offer next steps:**
109 - `{{COMMAND_PREFIX}}new-milestone` — start next milestone (questioning → research → requirements → roadmap)
110
111</process>
112
113<success_criteria>
114
115- Milestone archived to `.planning/milestones/v{{version}}-ROADMAP.md`
116- Requirements archived to `.planning/milestones/v{{version}}-REQUIREMENTS.md`
117- `.planning/REQUIREMENTS.md` deleted (fresh for next milestone)
118- ROADMAP.md collapsed to one-line entry
119- PROJECT.md updated with current state
120- Git tag v{{version}} created
121- Commit successful
122- User knows next steps (including need for fresh requirements)
123 </success_criteria>
124
125<critical_rules>
126
127- **Load workflow first:** Read complete-milestone.md before executing
128- **Verify completion:** All phases must have SUMMARY.md files
129- **User confirmation:** Wait for approval at verification gates
130- **Archive before deleting:** Always create archive files before updating/deleting originals
131- **One-line summary:** Collapsed milestone in ROADMAP.md should be single line with link
132- **Context efficiency:** Archive keeps ROADMAP.md and REQUIREMENTS.md constant size per milestone
133- **Fresh requirements:** Next milestone starts with `{{COMMAND_PREFIX}}new-milestone` which includes requirements definition
134 </critical_rules>