gsd-milestone-summary

Generate a milestone summary document from project planning artifacts for team onboarding.

Updated Feb 18, 2026
One-click install
npx skills add https://github.com/jjchambers80/judgesdirectory --skill gsd-milestone-summary-jjchambers80
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-milestone-summary
Source: https://github.com/jjchambers80/judgesdirectory/tree/main/.github/skills/gsd-milestone-summary
Command: npx skills add https://github.com/jjchambers80/judgesdirectory --skill gsd-milestone-summary-jjchambers80

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After a milestone ships, project knowledge is scattered across roadmaps, requirement files, phase summaries, and verification reports, making it hard for new team members or reviewers to understand what was built and why. ## Core Features & Use Cases - Artifact Aggregation: Reads ROADMAP, REQUIREMENTS, CONTEXT, SUMMARY, VERIFICATION, RESEARCH, and RETROSPECTIVE files from the .planning directory, including archived milestone versions. - Structured Summary Generation: Produces a seven-section MILESTONE_SUMMARY document covering Overview, Architecture, Phases, Decisions, Requirements, Tech Debt, and Getting Started, written to .planning/reports/. - Use Case: A new engineer joins after milestone v2 ships. Run the skill with version v2 to generate one readable document explaining the entire milestone, then ask follow-up questions in an interactive Q&A session. ## Quick Start Ask the assistant to generate a milestone summary for version v2 using the gsd-milestone-summary skill.

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 for new team members?▼

Run the skill with an optional version argument, and it reads all milestone artifacts from the .planning directory, then writes a seven-section MILESTONE_SUMMARY document to .planning/reports/ and presents it inline for review.

What files does the milestone summary skill read?▼

It reads ROADMAP.md, PROJECT.md, STATE.md, RETROSPECTIVE.md, archived milestone ROADMAP and REQUIREMENTS files, and per-phase SUMMARY, VERIFICATION, CONTEXT, and RESEARCH files under .planning/phases/.

Can I generate a summary for an older archived milestone version?▼

Yes. Pass the version as an argument, and the skill resolves it from archived files like .planning/milestones/v{version}-ROADMAP.md. Without an argument, it defaults to the current or latest milestone from STATE.md.

What sections are included in the milestone summary output?▼

The generated document contains seven sections: Overview, Architecture, Phases, Decisions, Requirements, Tech Debt, and Getting Started, giving readers a complete picture of what was built, how, and why.

What happens if some milestone artifacts are missing?▼

The skill reads all available artifacts and resolves the version from arguments, STATE.md, or an archive scan. Missing optional files like archived REQUIREMENTS are skipped, but core artifacts are needed for a complete summary.