gsd-cleanup

To archive completed phase directories, the workflow identifies finished milestones under .planning/phases and moves them into milestone-specific storage folders. It preserves the historical phase organization inside .planning/milestones/v{X.Y}-phases during the cleanup process.

Yes, you can review what gets archived by generating a dry-run summary. This summary displays the completed milestones and their associated phase directories planned for archival, requiring your explicit confirmation before any files are actually moved.

Milestone detection for phase cleanup works by scanning the .planning/phases directory to separate completed milestones from active work. It identifies finished phase folders and groups them by their corresponding milestone versions for accurate archival.

The best way to organize finished milestone phases is to move them from .planning/phases into milestone-specific archive folders. This approach preserves cleanup history and maintains project organization under the .planning/milestones/v{X.Y}-phases structure.

Yes, phase archival requires confirmation gating before moving any directories. After generating a dry-run summary of the completed milestones, the workflow pauses and waits for your explicit approval to proceed with the actual archival.

You should archive completed milestone phases instead of deleting them when you need to preserve cleanup history and maintain historical project organization. Archival moves the directories into milestone-specific storage rather than permanently removing them.