Files
get-shit-done/commands/gsd/milestone-summary.md
Tom Boucher e4ca76dbb7 fix: address all review findings on PR #1299
Remaining items from adversarial review:
- Add type: prompt to command frontmatter (consistency with complete-milestone)
- Replace git stats step with 4-method fallback chain (tag → STATE.md date →
  earliest phase commit → skip gracefully)
- Add 7 fixture-based behavioral tests: archived milestone discovery,
  multi-phase artifact discovery with varying completeness, empty .planning/
  handling, output filename validation, git stats fallback verification,
  type: prompt frontmatter check

Tests: 25/25 milestone-summary, 1236/1236 full suite

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

1.9 KiB

type, name, description, argument-hint, allowed-tools
type name description argument-hint allowed-tools
prompt 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>