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