gsd-cleanup

To archive completed milestone phase directories, you can run an automated cleanup workflow that moves them into a versioned .planning/milestones/v{X.Y}-phases/ location. This keeps active planning spaces lean and reduces clutter in live repositories.

Yes, you can preview what will be archived by running a dry-run summary before actual archiving. This safe confirmation workflow generates a summary of matching milestone phase directories so you can verify what would be moved.

The best way to organize versioned milestone archives is to move completed phase directories into a dedicated .planning/milestones/v{X.Y}-phases/ location. This provides traceability and ensures active planning spaces remain uncluttered.

Automated milestone archival handles versioning by generating a versioned path and moving completed phase directories into .planning/milestones/v{X.Y}-phases/. This ensures archived milestones are stored with traceability and are undo-ready.

Yes, you need manual confirmation before the cleanup tool moves your milestone folders. After running the initial command, it provides a dry-run summary and requires a safe confirmation workflow to proceed with actual archiving.

You should archive completed milestones to keep active planning spaces lean and reduce clutter in live repositories. Moving phase directories to a dedicated history location ensures traceability without interfering with ongoing work.