Files
msd-core/commands/gsd/milestone-summary.md
Tom Boucher 679243b09a fix: address review findings on milestone-summary PR
1. Add <success_criteria> section to command (pattern compliance)
2. Fix archived audit path: check .planning/milestones/ not .planning/
3. Add RESEARCH.md to command context block
4. Add empty phase handling (graceful skip to minimal summary)
5. Add overwrite guard for existing summary files
6. Add 7 new tests: overwrite guard, empty phases, audit paths,
   success_criteria, RESEARCH.md context, artifact path resolution

Tests: 18/18 milestone-summary, 1184/1184 full suite

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-03-21 16:31:13 -04:00

1.9 KiB

name, description, argument-hint, allowed-tools
name description argument-hint allowed-tools
gsd:milestone-summary Generate a comprehensive project summary from milestone artifacts for team onboarding and review [version]
Read
Write
Bash
Grep
Glob
Generate a structured milestone summary for team onboarding and project review. Reads completed milestone artifacts (ROADMAP, REQUIREMENTS, CONTEXT, SUMMARY, VERIFICATION files) and produces a human-friendly overview of what was built, how, and why.

Purpose: Enable new team members to understand a completed project by reading one document and asking follow-up questions. Output: MILESTONE_SUMMARY written to .planning/reports/, presented inline, optional interactive Q&A.

<execution_context> @~/.claude/get-shit-done/workflows/milestone-summary.md </execution_context>

**Project files:** - `.planning/ROADMAP.md` - `.planning/PROJECT.md` - `.planning/STATE.md` - `.planning/RETROSPECTIVE.md` - `.planning/milestones/v{version}-ROADMAP.md` (if archived) - `.planning/milestones/v{version}-REQUIREMENTS.md` (if archived) - `.planning/phases/*-*/` (SUMMARY.md, VERIFICATION.md, CONTEXT.md, RESEARCH.md)

User input:

  • Version: $ARGUMENTS (optional — defaults to current/latest milestone)
Read and execute the milestone-summary workflow from @~/.claude/get-shit-done/workflows/milestone-summary.md end-to-end.

<success_criteria>

  • Milestone version resolved (from args, STATE.md, or archive scan)
  • All available artifacts read (ROADMAP, REQUIREMENTS, CONTEXT, SUMMARY, VERIFICATION, RESEARCH, RETROSPECTIVE)
  • Summary document written to .planning/reports/MILESTONE_SUMMARY-v{version}.md
  • All 7 sections generated (Overview, Architecture, Phases, Decisions, Requirements, Tech Debt, Getting Started)
  • Summary presented inline to user
  • Interactive Q&A offered
  • STATE.md updated </success_criteria>