gsd-cleanup

To archive completed milestone phases automatically, run the cleanup workflow to identify finished phases in .planning/phases/ and move them into .planning/milestones/v{X.Y}-phases/. The process shows a dry-run summary before moving any files on confirmation.

The best way to clean up accumulated phase directories is using an automated archival workflow that moves completed milestone phases from .planning/phases/ into a dedicated .planning/milestones/v{X.Y}-phases/ location, keeping planning areas tidy without manual file management.

Yes, you can preview changes before archiving milestone phase directories because the workflow provides a dry-run summary. This summary identifies completed milestones and shows exactly what will be archived before you confirm the operation.

Yes, it is safe to run milestone phase cleanup multiple times because the workflow ensures idempotent operation. Repeated runs will not duplicate or misplace data, preventing accidental overwrites when archiving completed phases into .planning/milestones/.

Yes, you need the deterministic cleanup workflow defined at @$HOME/.claude/get-shit-done/workflows/cleanup.md to automate milestone archival. This configuration file ensures safe archival operations by dictating the identification and moving logic.

You should not use automated archival for completed milestone phases when directories are still actively in use or lack the expected .planning/phases/ structure. The workflow targets completed milestones, so active phase directories remain untouched.