Generate a human-readable milestone summary from the planning artifacts (ROADMAP, REQUIREMENTS, per-phase CONTEXT/SUMMARY/VERIFICATION) covering architecture, phases, key decisions, requirements, and tech debt. Use when someone needs to understand a finished or in-progress milestone from one document, for team onboarding or review.
Scanned 9/6/2026
Install to Claude Code
npx -y skills add D0NMEGA/donnyclaude --skill donny-milestone-summary --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Donny Milestone Summary?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/d0nmega-donny-milestone-summary)More formats (shields.io, HTML) on the badges page.
---
name: donny-milestone-summary
description: "Generate a human-readable milestone summary from the planning artifacts (ROADMAP, REQUIREMENTS, per-phase CONTEXT/SUMMARY/VERIFICATION) covering architecture, phases, key decisions, requirements, and tech debt. Use when someone needs to understand a finished or in-progress milestone from one document, for team onboarding or review."
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>
@~/.claude/donny/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 @~/.claude/donny/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>
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!