Mechanical rename produced by scripts/msd-rename.cjs: gsd/Gsd/GSD -> msd/Msd/MSD across contents and paths, upstream package/repo coordinates -> @golem15/msd-core and golem15com/msd-core. Deep links into upstream history, sibling upstream packages, the GSD-2 import feature, CHANGELOG.md and .changeset/ are kept as-is. Hand edits on top: MSD block-letter banner and logos, LICENSE copyright line, package/plugin identity, regenerated lockfile, install-tree fixtures, derived registries and benchmark baseline; migration checksum baseline re-locked (MSD keeps its own install state, so no install had applied the old sums); sort-order and regex-escaped expectations in tests adjusted.
52 lines
1.8 KiB
Markdown
52 lines
1.8 KiB
Markdown
---
|
|
type: prompt
|
|
name: msd:milestone-summary
|
|
description: Generate a comprehensive project summary from milestone artifacts for team onboarding and review
|
|
argument-hint: "[version]"
|
|
allowed-tools:
|
|
- Read
|
|
- Write
|
|
- Bash
|
|
- Grep
|
|
- Glob
|
|
---
|
|
|
|
<objective>
|
|
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.
|
|
</objective>
|
|
|
|
<execution_context>
|
|
@~/.claude/msd-core/workflows/milestone-summary.md
|
|
</execution_context>
|
|
|
|
<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)
|
|
</context>
|
|
|
|
<process>
|
|
Execute end-to-end.
|
|
</process>
|
|
|
|
<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>
|