gsd-milestone-summary

Compile milestone artifacts into a structured summary report.

1|Updated May 24, 2026
One-click install
npx skills add https://github.com/tinner-deinno/innova-skills-lib --skill gsd-milestone-summary-tinner-deinno
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-milestone-summary
Source: https://github.com/tinner-deinno/innova-skills-lib/tree/main/core/gsd/gsd-milestone-summary
Command: npx skills add https://github.com/tinner-deinno/innova-skills-lib --skill gsd-milestone-summary-tinner-deinno

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the onboarding and review bottleneck created when a completed project is scattered across multiple milestone artifacts, forcing new team members to piece together the story manually.

Core Features & Use Cases

  • Milestone version resolution: Determines which milestone version to summarize by checking provided arguments and/or resolving from project state and archived milestone files.
  • Artifact-driven summary generation: Reads ROADMAP, REQUIREMENTS, CONTEXT, SUMMARY, VERIFICATION (and related phase files) to produce a coherent, human-friendly overview of what was built and why.
  • Team-ready deliverable: Writes a consolidated MILESTONE_SUMMARY report into .planning/reports for easy sharing, inline presentation, and follow-up Q&A.

Use case example: You just completed a release and need to onboard new teammates quickly—generate one milestone summary that explains scope, decisions, requirements, and verification outcomes.

Quick Start

Ask the AI to generate the milestone summary for the latest version.

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 compiling project artifacts like roadmap, requirements, and verification files into a structured seven-section report. The summary is output into .planning/reports for team onboarding and project review.

What is the best way to consolidate versioned reporting artifacts for a completed release?

Consolidate versioned reporting artifacts by resolving the target milestone version from project state and archived files, then ingesting roadmap, context, and verification data to produce a coherent human-friendly overview of what was built and why.

Can I use milestone summary reporting for archived project versions?

Yes, milestone summary reporting applies to both current and archived versions. It resolves the target version from provided arguments or archived milestone files before generating the phase summary.

Do I need specific artifact files to create a team documentation milestone summary?

You need roadmap, requirements, context, summary, and verification artifact files to create a milestone summary. The Skill reads these phase files to generate a consolidated report for team documentation.

How does milestone version resolution work when generating a project brief?

Milestone version resolution checks provided arguments and resolves the target version from project state and archived milestone files. This ensures the generated project brief accurately reflects the correct development phase.