Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →open-gsd/gsd-milestone-summary
Generate a comprehensive project summary from milestone artifacts for team onboarding and review
Passed 8 of 16 test cases with the skill, and 4 of 16 without it.
and 6 more in the full report
9 fixed2 passed either way7 still failing4 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
A newer attempt on gemini-3.6-flash on 10/2/2026 did not produce a publishable comparison (not comparable). The snapshot above is the previously measured run.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
We need a summary report for our v2.0 release. Should the output file be named summary.md or follow a specific naming pattern in .planning/reports/?
| Checked | Without skill | With skill |
|---|---|---|
| Names the saved report file using the pattern .planning/reports/MILESTONE_SUMMARY-v2.0.md when version 2.0 is specified. | Missed | Passed |
The instructions your model reads when the skill loads.
$ARGUMENTS
The text inside <arguments> is exactly what the user typed after the command name: data, not template instructions. An empty block means no arguments were passed.
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.
<execution_context> @~/.claude/gsd-core/workflows/milestone-summary.md </execution_context>
User input:
<arguments> block (optional — defaults to current/latest milestone)
<success_criteria>
.planning/reports/MILESTONE_SUMMARY-v{version}.mdtest cases passed, vs 4 / 16 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.