gsd-cleanup

Archive completed milestone phase directories into .planning/milestones/v{X.Y}-phases/ after a dry-run.

1|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/TruCol270/salty-pickle --skill gsd-cleanup-trucol270
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-cleanup
Source: https://github.com/TruCol270/salty-pickle/tree/main/.claude-skills/gsd-cleanup
Command: npx skills add https://github.com/TruCol270/salty-pickle --skill gsd-cleanup-trucol270

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive completed milestone phase directories into a centralized, organized structure to keep active planning clean and prevent drift.

Core Features & Use Cases

  • Automatically detect completed milestones and archive their phase directories into .planning/milestones/v{X.Y}-phases/.
  • Provide a dry-run preview before performing archival actions.
  • Require explicit user confirmation to finalize the archiving, ensuring safety and traceability.

Quick Start

Run the cleanup workflow to archive completed milestone phases into the .planning/milestones/v{X.Y}-phases/ directory after a dry-run.

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 to keep my planning clean?

Milestone archiving works by detecting completed phases and relocating their directories into a standardized .planning/milestones/v{X.Y}-phases/ structure, requiring explicit confirmation before finalizing the move.

Can I preview milestone archiving before making changes to the filesystem?

Yes, you can preview milestone archiving using the dry-run feature, which scans the filesystem for completed phases and displays the planned archival actions before requiring explicit confirmation to execute.

What is the best way to organize old project phase directories that accumulate over time?

The best way to organize accumulated phase directories is to archive them into a centralized .planning/milestones/v{X.Y}-phases/ structure, automatically detecting completed milestones and consolidating their folders to prevent planning drift.

Does the cleanup workflow require confirmation before moving files?

Yes, the cleanup workflow requires explicit user confirmation to finalize archiving, ensuring safety and traceability after the dry-run preview identifies which completed milestone phases will be moved.

When should I archive milestone phases in my project workflow?

You should archive milestone phases when completed directories accumulate over time and begin causing active planning drift, using the cleanup workflow to safely relocate them into the versioned .planning/milestones/ structure.