gsd-complete-milestone
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.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-11
- Stars
- ★ 631
- Forks
- 15
01 前言 Front Matter
- name
- gsd-complete-milestone
- 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.
- allowed-tools
- [ "Read", "Write", "Bash" ]
- argument-hint
- <version>
03 SKILL.md 正文
<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:
-
Check for audit:
- Look for
.planning/v$ARGUMENTS-MILESTONE-AUDIT.md - If missing or stale: recommend
/gsd-audit-milestonefirst - If audit status is
gaps_found: recommend/gsd-plan-milestone-gapsfirst - If audit status is
passed: proceed to step 1
## 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. - Look for
-
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$ARGUMENTS-ROADMAP.md - Extract full phase details from ROADMAP.md
- Fill milestone-archive.md template
- Update ROADMAP.md to one-line summary with link
- Create
-
Archive requirements:
- Create
.planning/milestones/v$ARGUMENTS-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)
- Create
-
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: .planning/ROADMAP.md, PROJECT.md, STATE.md, milestones/ archives
- Commit:
chore: archive v$ARGUMENTS milestone - Tag:
git tag -a v$ARGUMENTS -m "[milestone summary]" - Ask about pushing tag
-
Offer next steps:
/gsd-new-milestone— start next milestone (questioning → research → requirements → roadmap)
</process>
<success_criteria>
- Milestone archived to
.planning/milestones/v$ARGUMENTS-ROADMAP.md - Requirements archived to
.planning/milestones/v$ARGUMENTS-REQUIREMENTS.md .planning/REQUIREMENTS.mddeleted (fresh for next milestone)- ROADMAP.md collapsed to one-line entry
- PROJECT.md updated with current state
- Git tag v$ARGUMENTS created
- Commit successful
- User knows next steps (including need for fresh requirements) </success_criteria>
<critical_rules>
- 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
/gsd-new-milestonewhich includes requirements definition </critical_rules>
04 同仓库更多 Skills
trading-super-intelligence
Trading Super Intelligence Team. Named real-world personas across 8 cells. Built local-first (LM Studio) and validator-gated. Illustrative composites; see DISCLAIMER.md.
strategy-super-intelligence
Strategy Super Intelligence Team. Named real-world personas across 7 cells. Built local-first (LM Studio) and validator-gated. Illustrative composites; see DISCLAIMER.md.
risk-compliance-super-intelligence
Risk & Compliance (GRC) Super Intelligence Team. Named real-world personas across 7 cells. Built local-first (LM Studio) and validator-gated. Illustrative composites; see DISCLAIMER.md.
product-design-super-intelligence
Your product + design brain trust and decision partner. Named personas across 8 cells spanning product strategy, discovery/research, growth/metrics, design foundations/usability, design leadership/craft, UX/content, design systems, and a…
legal-ip-super-intelligence
Your legal, IP, and regulatory brain trust. 31 named personas across 7 cells covering patent strategy, tech licensing, regulatory litigation, AI governance, open-source compliance, privacy law, and antitrust.
healthcare-life-sciences-super-intelligence
Your healthcare and life sciences brain trust. 25 named personas across 7 cells covering drug discovery, medtech, biotech strategy, health policy, genomics, clinical trials, and healthcare economics.