Display completed milestones from the MILESTONES.md registry
Scanned 2/12/2026
Install via CLI
openskills install majiayu000/claude-skill-registry---
name: gsd-list-milestones
description: Display completed milestones from the MILESTONES.md registry
allowed-tools: Read, Bash
---
<objective>
Display completed milestones from the MILESTONES.md registry.
Purpose: Show milestone history without scanning filesystem.
Output: Formatted list of completed milestones with key accomplishments.
</objective>
<execution_context>
@.github/get-shit-done/references/ui-brand.md
</execution_context>
<context>
Registry file:
- `.planning/MILESTONES.md` — Milestone completion registry
</context>
<process>
<step name="check_registry_exists">
Check if milestone registry exists using bash:
```bash
if [ ! -f .planning/MILESTONES.md ]; then
echo ""
echo "No milestones completed yet."
echo ""
echo "Complete your first milestone with:"
echo " /gsd-complete-milestone"
echo ""
exit 0
fi
```
If registry doesn't exist: Show friendly message and exit.
If registry exists: Continue to display step.
</step>
<step name="display_milestones">
Display milestone history from registry:
```bash
echo ""
echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
echo " GSD ► MILESTONE HISTORY"
echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
echo ""
# Display registry content
cat .planning/MILESTONES.md
echo ""
echo "───────────────────────────────────────────────────────────────"
echo ""
echo "Archived milestones are in: .planning/history/"
echo ""
echo "To view archived files:"
echo " ls .planning/history/v1.0/"
echo " cat .planning/history/v1.0/ROADMAP.md"
echo ""
echo "To start new milestone:"
echo " /gsd-new-milestone"
echo ""
echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
```
</step>
</process>
<success_criteria>
- [ ] Registry existence checked before display
- [ ] Friendly message if no milestones completed yet
- [ ] MILESTONES.md content displayed directly (no parsing)
- [ ] Helpful bash commands shown for accessing archives
- [ ] User knows next command (complete-milestone or new-milestone)
- [ ] Template variables (/gsd-) used for cross-platform support
</success_criteria>
No comments yet. Be the first to comment!
Playbook for creating and editing uCoz landing pages via MCP tools (`templates_tool`, `ftp_tool`, `modules_tool`). Use for tasks such as: "build a landing page", "update the homepage as a landing page", "create a promo page on the homepage", "add a lead form / menu / SEO to the homepage". Homepage: `page_list`, `page_get`; first publish — `page_update` with full `page_tmpl`; HTML edits after generation — `patch_template` (module_id=2, template_id=1), not `update_template`. Activate the mail f...
Interact with the Paperclip control plane API to manage tasks, coordinate with other agents, and follow company governance. Use when you need to check assignments, update task status, delegate work, post comments, set up or manage routines (recurring scheduled tasks), or call any Paperclip API endpoint. Do NOT use for the actual domain work itself (writing code, research, etc.) — only for Paperclip coordination.
Digital Audio Workstation usage, music composition, interactive music systems, and game audio implementation for immersive soundscapes.
Instantly.ai cold email outreach API - manage campaigns, leads, accounts, and analytics. Use for cold email automation, lead management, campaign creation/monitoring, and email account warmup.
Run a single Terminal-Bench problem through Paperclip in a bounded, human-in-the-loop improvement cycle until the smoke passes, the board rejects the next fix, the iteration budget is exhausted, or a real blocker is named. Each iteration runs a bounded smoke against an isolated Paperclip App worktree, captures artifacts, diagnoses the exact stop point with `/diagnose-why-work-stopped`, requests board confirmation before any product fix, then reruns against the same worktree. Use whenever an i...