gsd-milestone-summary

Generate a structured MILESTONE_SUMMARY report from milestone artifacts and update STATE.md.

Updated May 21, 2026
One-click install
npx skills add https://github.com/jedmamosto/m-and-ms --skill gsd-milestone-summary-jedmamosto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-milestone-summary
Source: https://github.com/jedmamosto/m-and-ms/tree/main/.agents/skills/gsd-milestone-summary
Command: npx skills add https://github.com/jedmamosto/m-and-ms --skill gsd-milestone-summary-jedmamosto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams lose context when milestones are scattered across multiple files, slowing onboarding and making reviews inconsistent.

Core Features & Use Cases

  • Milestone overview generation: Converts milestone artifacts into a single, human-friendly project summary for team onboarding and review.
  • Structured reporting across phases: Synthesizes ROADMAP, REQUIREMENTS, CONTEXT, SUMMARY, and VERIFICATION (plus research/retrospective where available) into a consistent format.
  • Actionable follow-up: Enables an optional interactive Q&A so new contributors can quickly identify unknowns and decisions.

Quick Start

Run gsd-milestone-summary to generate a comprehensive summary for the latest or specified milestone version and write it to .planning/reports/.

Frequently Asked Questions about gsd-milestone-summary

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a project milestone summary from scattered artifacts for onboarding?

Generate a milestone summary by reading ROADMAP, REQUIREMENTS, CONTEXT, SUMMARY, and VERIFICATION artifacts, then consolidating them into a single formatted MILESTONE_SUMMARY report for new contributor onboarding and project review.

What is the best way to consolidate project documentation for a specific version review?

Consolidate project documentation by resolving the target milestone version from arguments or archive state files, synthesizing all available artifacts into a consistent format that captures research and retrospective data for comprehensive version review.

Does milestone summary generation work without research or retrospective files?

Milestone summary generation works without research or retrospective files by treating them as optional, requiring only ROADMAP, REQUIREMENTS, CONTEXT, SUMMARY, and VERIFICATION artifacts to produce the structured onboarding report.

How do I resolve the milestone version when generating a project summary?

Resolve the milestone version by explicitly passing it as an argument when running the summary generation, or automatically reading the current version from existing archive and state files if no argument is provided.

Can I use milestone summaries to identify unknowns and decisions for new contributors?

You can use milestone summaries to identify unknowns and decisions through an optional interactive Q&A feature, enabling new contributors to quickly surface unresolved questions and track historical project decisions during onboarding.