gsd-cleanup

Archive completed milestone phase directories from `.planning/phases/` into `.planning/milestones/v{X.Y}-phases/`.

Updated Aug 23, 2026

Search Tags:#planning #workflow automation #directory management #GSD #project cleanup #milestone archiving

Ready to run

npx skills add https://github.com/BeiBei-Clic/ai-skills --skill gsd-cleanup-beibei-clic

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gsd-cleanup
Source: https://github.com/BeiBei-Clic/ai-skills/tree/main/gsd-cleanup
Command: npx skills add https://github.com/BeiBei-Clic/ai-skills --skill gsd-cleanup-beibei-clic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents project directories from growing endlessly by archiving phase folders from milestones that have already been completed.

Core Features & Use Cases

Milestone Cleanup: Detects completed milestones and targets their accumulated phase directories for archiving.
Structured Archival: Moves archived phase directories into .planning/milestones/v{X.Y}-phases/ to keep history organized.
Safe Execution Flow: Runs an end-to-end cleanup workflow that includes a dry-run summary before any changes are confirmed.

Use case: You have been running multi-phase project iterations and notice .planning/phases/ contains leftover phase directories from past milestones; this skill tidies them into the milestone versioned archive.

Quick Start

Run the cleanup workflow to archive completed milestone phase directories from your .planning/phases/ 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 a GSD project planning workspace?▼

To archive completed milestone phase directories, identify completed milestones, generate a dry-run summary of the targeted phases, and confirm the archival. This moves phase artifacts from `.planning/phases/` into `.planning/milestones/v{X.Y}-phases/`.

Why does my project planning directory keep accumulating old phase artifacts, and how can I clean them up?▼

Project planning directories accumulate old phase artifacts because completed milestone phases are left in the active workspace. You can clean them up by running an end-to-end workflow that archives these directories into versioned milestone folders.

Can I preview which phase directories will be archived before making any changes to my active phases?▼

Yes, you can preview changes through a dry-run summary generated before any directory modifications occur. This safe execution flow lists the completed milestone phase directories targeted for archival, requiring your confirmation before moving them.

Does milestone archiving work with any project directory structure, or does it require a specific GSD-style format?▼

Milestone archiving requires a specific GSD-style project planning directory structure. The workflow targets the `.planning/phases/` directory to collect past milestone artifacts and archives them into `.planning/milestones/v{X.Y}-phases/`.

What is the best way to organize past milestone artifacts without losing project history?▼

The best way to organize past milestone artifacts is structured archival into versioned directories. This workflow moves completed phase folders into `.planning/milestones/v{X.Y}-phases/`, keeping your active phases clean while preserving history.

What happens to phase directories if I do not run a project cleanup workflow after a milestone is completed?▼

If you do not run a project cleanup workflow, your `.planning/phases/` directory will grow endlessly as leftover phase directories from past milestones accumulate. This clutters the active phases workspace with outdated artifacts.