Skip to content
Back to skills

Gsd Milestone Summary

ASecurity

Use when onboarding someone to a finished milestone or preparing a team review. Reads ROADMAP, REQUIREMENTS, CONTEXT, SUMMARY, and VERIFICATION artifacts into one MILESTONE_SUMMARY in .planning/reports/, then offers Q&A.

  • 434 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 23, 2026
ai-agentsbash

Security analysis

A100/100

Scanned September 23, 2026

npx -y skills add coco-research/coco --skill gsd-milestone-summary --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Gsd Milestone Summary?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Gsd Milestone Summary
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/coco-research-gsd-milestone-summary/badge)](https://www.skillsdirectory.com/skills/coco-research-gsd-milestone-summary)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: gsd-milestone-summary
description: "Use when onboarding someone to a finished milestone or preparing a team review. Reads ROADMAP, REQUIREMENTS, CONTEXT, SUMMARY, and VERIFICATION artifacts into one MILESTONE_SUMMARY in .planning/reports/, then offers Q&A."
argument-hint: "[version]"
allowed-tools:
  - Read
  - Write
  - Bash
  - Grep
  - Glob
---


<objective>
Generate a structured milestone summary for team onboarding and project review. Reads completed milestone artifacts (ROADMAP, REQUIREMENTS, CONTEXT, SUMMARY, VERIFICATION files) and produces a human-friendly overview of what was built, how, and why.

Purpose: Enable new team members to understand a completed project by reading one document and asking follow-up questions.
Output: MILESTONE_SUMMARY written to `.planning/reports/`, presented inline, optional interactive Q&A.
</objective>

<execution_context>
@$HOME/.claude/get-shit-done/workflows/milestone-summary.md
</execution_context>

<context>
**Project files:**
- `.planning/ROADMAP.md`
- `.planning/PROJECT.md`
- `.planning/STATE.md`
- `.planning/RETROSPECTIVE.md`
- `.planning/milestones/v{version}-ROADMAP.md` (if archived)
- `.planning/milestones/v{version}-REQUIREMENTS.md` (if archived)
- `.planning/phases/*-*/` (SUMMARY.md, VERIFICATION.md, CONTEXT.md, RESEARCH.md)

**User input:**
- Version: $ARGUMENTS (optional — defaults to current/latest milestone)
</context>

<process>
Read and execute the milestone-summary workflow from @$HOME/.claude/get-shit-done/workflows/milestone-summary.md end-to-end.
</process>

<success_criteria>
- Milestone version resolved (from args, STATE.md, or archive scan)
- All available artifacts read (ROADMAP, REQUIREMENTS, CONTEXT, SUMMARY, VERIFICATION, RESEARCH, RETROSPECTIVE)
- Summary document written to `.planning/reports/MILESTONE_SUMMARY-v{version}.md`
- All 7 sections generated (Overview, Architecture, Phases, Decisions, Requirements, Tech Debt, Getting Started)
- Summary presented inline to user
- Interactive Q&A offered
- STATE.md updated
</success_criteria>

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…