Use gsd-complete-milestone instead. This command has been unified into the completion workflow. Shows deprecation notice and exits.
Scanned 2/12/2026
Install via CLI
Skills Directoryopenskills install majiayu000/claude-skill-registry---
name: gsd-archive-milestone
description: Use gsd-complete-milestone instead. This command has been unified into the completion workflow. Shows deprecation notice and exits.
allowed-tools: Read
---
# Archive Milestone (DEPRECATED)
**This command has been replaced by gsd-complete-milestone.**
<objective>
DEPRECATED: This command has been unified into gsd-complete-milestone.
</objective>
<process>
<step name="show_deprecation_and_exit">
Display deprecation notice using GSD branded banner format:
```
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
GSD ► DEPRECATED
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
This command has been unified into the milestone completion workflow.
**Old workflow (deprecated):**
1. {{COMMAND_PREFIX}}complete-milestone # Mark complete
2. {{COMMAND_PREFIX}}archive-milestone # Move to milestones/ ← YOU ARE HERE
3. {{COMMAND_PREFIX}}restore-milestone # Retrieve from milestones/
**New workflow (unified):**
{{COMMAND_PREFIX}}complete-milestone # Archives directly to history/v{X.Y}/
All milestone files now move directly to `.planning/history/v{X.Y}/`
with mirrored directory structure during completion. Archives are
permanent and git-tracked.
───────────────────────────────────────────────────────────────
## Why This Changed
The old multi-step workflow created confusion about when files were
truly archived. The new unified workflow moves everything to permanent
history/ storage in a single atomic operation.
**To review archived milestones:**
{{COMMAND_PREFIX}}list-milestones
**To start new milestone:**
{{COMMAND_PREFIX}}new-milestone
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
```
Exit immediately without executing any operations.
</step>
</process>
<success_criteria>
- [ ] Deprecation message displayed with branded banner
- [ ] Clear explanation of old vs new workflow
- [ ] User directed to correct command (complete-milestone)
- [ ] No file operations executed
- [ ] Template variables ({{COMMAND_PREFIX}}) 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...
