gsd-cleanup

Archive completed milestone phase directories into versioned .planning/milestones folders.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/Poom5741/eggo-world-pb --skill gsd-cleanup-poom5741
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-cleanup
Source: https://github.com/Poom5741/eggo-world-pb/tree/main/.qwen/skills/gsd-cleanup
Command: npx skills add https://github.com/Poom5741/eggo-world-pb --skill gsd-cleanup-poom5741

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive completed milestone phase directories into the .planning/milestones/v{X.Y}-phases/ to maintain a clean project history and fast retrospectives.

Core Features & Use Cases

  • Automatic archival of phase directories for completed milestones.
  • Dry-run preview and user-confirmed archival to prevent data loss.
  • Works with existing .planning/phases/ and archives to versioned v{X.Y}-phases folders.

Quick Start

Run the cleanup workflow to archive completed milestone phase directories after reviewing a dry-run summary.

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 automatically?

You can archive completed milestone phase directories automatically by running a Bash workflow that moves them from .planning/phases/ into versioned .planning/milestones/v{X.Y}-phases/ folders. This process maintains a clean project history and enables fast retrospectives.

Can I preview phase directory archival before moving files?

Yes, you can preview phase directory archival before moving files by using the dry-run preview feature. The workflow generates a dry-run summary of completed milestones and requires user confirmation to prevent data loss before performing deterministic archival.

What is the best way to clean up accumulated .planning/phases/ directories?

The best way to clean up accumulated .planning/phases/ directories is to use an automated archival workflow that identifies completed milestones and safely relocates their phase folders into versioned v{X.Y}-phases directories under .planning/milestones/.

Does the milestone archival workflow require any specific dependencies?

No, the milestone archival workflow does not require any specific dependencies or components. It operates as a standalone Bash workflow to identify completed milestones and execute safe, deterministic archival of phase directories.

How does deterministic archival work for versioned milestone phases?

Deterministic archival for versioned milestone phases works by consistently relocating completed phase directories from .planning/phases/ into specifically structured v{X.Y}-phases folders. This Bash workflow ensures project history remains clean and predictable after user confirmation.