gsd-milestone-summary

Name: gsd-milestone-summary
Availability: InStock
Author: trucol270

Read milestone artifacts and generate a structured MILESTONE_SUMMARY report.

1|Updated Apr 7, 2026

Search Tags:#versioning #documentation #onboarding #summary #project-management #milestone #artifact-analysis

Ready to run

npx skills add https://github.com/TruCol270/salty-pickle --skill gsd-milestone-summary-trucol270

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gsd-milestone-summary
Source: https://github.com/TruCol270/salty-pickle/tree/main/.claude-skills/gsd-milestone-summary
Command: npx skills add https://github.com/TruCol270/salty-pickle --skill gsd-milestone-summary-trucol270

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Onboarding new team members and conducting project reviews requires quickly understanding the current milestone state; without a single consolidated document, teams waste time piecing together multiple artifacts. This Skill reads milestone artifacts (ROADMAP, REQUIREMENTS, CONTEXT, SUMMARY, VERIFICATION, STATE, and archived milestones) and produces a comprehensive, human-friendly Milestone Summary that highlights what was built, how, and why.

Core Features & Use Cases

Reads milestone artifacts from the planning directory and archives.
Generates a structured Milestone Summary with sections such as Overview, Architecture, Phases, Decisions, Requirements, Tech Debt, and Getting Started.
Writes the final summary to .planning/reports/MILESTONE_SUMMARY-v{version}.md and supports interactive Q&A for follow-ups.

Quick Start

Generate the milestone summary for the latest milestone version and save it to .planning/reports/MILESTONE_SUMMARY-v{version}.md for team review.

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 milestone summary for project onboarding?▼

Generate a milestone summary by reading planning artifacts like ROADMAP, REQUIREMENTS, CONTEXT, SUMMARY, VERIFICATION, and STATE. It consolidates these files into a structured overview highlighting project phases, architecture, and decisions.

What is a milestone summary used for in project management?▼

A milestone summary is used for onboarding new members, conducting project reviews, and creating archival documentation. It provides a single consolidated document so teams avoid piecing together multiple planning artifacts.

How do I create versioned documentation for archived milestones?▼

Create versioned documentation by selecting a specific milestone version through arguments or archived milestones. The summary is written directly to .planning/reports/MILESTONE_SUMMARY-v{version}.md for team review.

Does this milestone summary tool require specific planning artifacts to exist?▼

Yes, it requires existing planning artifacts to function. It reads ROADMAP, REQUIREMENTS, CONTEXT, SUMMARY, VERIFICATION, and STATE files from your planning directory and archives to produce the final output.

What sections are included in a structured milestone summary?▼

A structured milestone summary includes sections for Overview, Architecture, Phases, Decisions, Requirements, Tech Debt, and Getting Started. It also supports interactive Q&A for follow-up questions after generation.

Can I use this for project reviews without manual document assembly?▼

Yes, you can use this for project reviews without manual assembly. It automatically extracts data from your planning directory to produce a human-friendly summary of what was built, how, and why.