gsd-cleanup

Archive completed milestone phase directories into versioned milestone archives.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/dobrinz123/claude-skills-share --skill gsd-cleanup-dobrinz123
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-cleanup
Source: https://github.com/dobrinz123/claude-skills-share/tree/main/skills/gsd-cleanup
Command: npx skills add https://github.com/dobrinz123/claude-skills-share --skill gsd-cleanup-dobrinz123

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes clutter by archiving accumulated phase directories left in .planning/phases after milestones complete, preserving milestone history and keeping the planning workspace organized.

Core Features & Use Cases

  • Identify completed milestones and locate their phase directories under .planning/phases.
  • Dry-run summaries that show which directories will be archived and the destination .planning/milestones/v{X.Y}-phases/ paths.
  • Confirmed archival that moves selected phase directories into versioned milestone archives to maintain a clean project structure. Use case: When multiple past milestones leave legacy phase folders in .planning/phases, run this workflow to review and archive them safely.

Quick Start

Show a dry-run of archivable phase directories and confirm to archive them into .planning/milestones/v{X.Y}-phases/.

Frequently Asked Questions about gsd-cleanup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I archive completed milestone phase directories in my project planning workspace?

To archive completed milestone phase directories, identify legacy folders under .planning/phases, generate a dry-run summary for review, and move them into .planning/milestones/v{X.Y}-phases/ after user confirmation to keep the workspace organized.

What is the best way to clean up clutter from past project milestones without losing history?

Cleaning up milestone clutter involves moving accumulated phase directories from .planning/phases into versioned milestone archives at .planning/milestones/v{X.Y}-phases/, preserving milestone history while maintaining a clean project structure.

Can I preview which phase directories will be moved before archiving them?

Yes, you can preview phase directory archival using the dry-run summary feature, which shows exactly which directories will be archived and their destination paths in .planning/milestones/v{X.Y}-phases/ before any moves are performed.

Does the milestone archival workflow require any external dependencies or tools?

No external dependencies are required for milestone archival. The workflow operates autonomously using built-in Read, Write, and Bash tools to identify completed milestones, present a dry-run review, and execute verified directory moves.

When should I archive phase directories from completed milestones in my project?

You should archive phase directories when a project's .planning/phases directory contains accumulated directories from past milestones, causing workspace clutter that needs to be safely moved into versioned milestone archive paths.

Why do legacy phase folders accumulate in the .planning/phases directory after milestones complete?

Legacy phase folders accumulate because completed milestones leave their phase directories behind in .planning/phases, requiring an archival workflow to move them into .planning/milestones/v{X.Y}-phases/ to preserve history and maintain organization.