gsd-milestone-summary

Generate structured milestone overviews from completed project artifacts.

4|1|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/lgwanai/openforce --skill gsd-milestone-summary-lgwanai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-milestone-summary
Source: https://github.com/lgwanai/openforce/tree/main/skills/gsd-milestone-summary
Command: npx skills add https://github.com/lgwanai/openforce --skill gsd-milestone-summary-lgwanai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates the time-consuming effort of piecing together what a project milestone achieved by automatically compiling existing milestone artifacts into one clear summary for quick onboarding and review.

Core Features & Use Cases

  • Milestone Artifact Aggregation: Reads roadmap, requirements, context, summaries, and verification materials (including optional phase and archived milestone files) to build a single coherent narrative.
  • Structured Deliverable Generation: Produces a standardized milestone overview with consistent sections (Overview, Architecture, Phases, Decisions, Requirements, Tech Debt, Getting Started).
  • Team-Usable Output: Writes the result to .planning/reports/ and presents it inline to support discussion and follow-up Q&A.

Quick Start

Run gsd-milestone-summary for your latest milestone version to generate a comprehensive team onboarding and review report.

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 completed project artifacts like ROADMAP, REQUIREMENTS, CONTEXT, SUMMARY, and VERIFICATION files. This Skill compiles them into a standardized team onboarding overview with seven sections.

What is the best way to compile project requirements and tech debt into a team-ready overview?

Compiling project requirements and tech debt into a team-ready overview is done by aggregating milestone artifacts into a standardized report with Architecture, Decisions, Requirements, and Tech Debt sections.

Does generating a milestone overview require specific project repository files?

Generating a milestone overview requires milestone-based repositories storing ROADMAP, REQUIREMENTS, CONTEXT, SUMMARY, and VERIFICATION files. It optionally includes phase summaries and archived version files.

Where does the milestone summary output get saved in the project directory?

The milestone summary output gets saved as MILESTONE_SUMMARY within the `.planning/reports/` directory. It is also presented inline to support discussion, interactive Q&A, and updates STATE.md.

Can I include phase summaries and archived version files when creating a project milestone report?

You can include optional phase summaries and archived version files when creating a project milestone report. The artifact resolution process reads all available inputs to satisfy end-to-end milestone aggregation.

What sections are included in a structured milestone overview for architecture review?

A structured milestone overview for architecture review includes seven required sections: Overview, Architecture, Phases, Decisions, Requirements, Tech Debt, and Getting Started.