gsd-cleanup

To archive old milestone phase directories, this skill moves accumulated folders from .planning/phases/ into versioned milestone archives under .planning/milestones/v{X.Y}-phases/. It only proceeds after you review a dry-run summary and provide explicit confirmation.

Yes, you can preview repository maintenance changes before archiving completed milestones using the built-in dry-run summary. This feature generates a detailed preview of what will be archived so you can review the impact on your project planning structure before committing.

The best way to reduce clutter from leftover phase folders is to run an automated archiving workflow that moves them into versioned milestone archives. This ensures completed milestone phases are reliably organized under .planning/milestones/ without manual file operations.

Yes, milestone management archiving works without additional dependencies. The skill operates independently to move accumulated phase directories from .planning/phases/ into versioned archive locations, requiring only your explicit confirmation after reviewing the dry-run summary.

You should not use automated archiving for project planning directories when your milestone phases are still active or incomplete. The archiving process is designed exclusively for completed milestones to prevent clutter, and it waits for explicit confirmation after the dry-run to protect active data.

Your .planning/phases/ directory accumulates old milestone folders because completed project phases are left behind after milestones finish. Archiving these accumulated directories into versioned milestone archives under .planning/milestones/ reliably reduces this repository clutter.