gsd-cleanup

Archive completed milestone phase directories into versioned folders after dry-run confirmation.

Updated Jan 25, 2026
One-click install
npx skills add https://github.com/MINT-IA/MINT --skill gsd-cleanup-mint-ia
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-cleanup
Source: https://github.com/MINT-IA/MINT/tree/main/.claude/skills/gsd-cleanup
Command: npx skills add https://github.com/MINT-IA/MINT --skill gsd-cleanup-mint-ia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill archives accumulated phase directories left in .planning/phases by identifying which directories belong to completed milestones and moving them into organized, versioned milestone archives under .planning/milestones/v{X.Y}-phases/, reducing clutter and preserving project history.

Core Features & Use Cases

  • Identify Completed Milestones: Scan .planning/phases to detect phase folders tied to milestones that are finished.
  • Dry-Run and Confirmation: Produce a clear dry-run summary of proposed moves and require explicit user confirmation before any changes.
  • Archive into Versioned Folders: Create and populate .planning/milestones/v{X.Y}-phases/ directories to keep phase history organized per milestone.
  • Use Case: After a milestone closes, consolidate its phase folders into the corresponding v{X.Y}-phases archive to declutter the active planning tree while preserving historical phases.

Quick Start

Archive completed phase directories from .planning/phases into .planning/milestones as a dry-run, review the proposed moves, and confirm to execute the archival process.

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 project phase directories into milestone folders?

To archive completed phase directories, scan .planning/phases to identify completed milestones and move them into versioned .planning/milestones/v{X.Y}-phases folders. This process requires a dry-run summary and explicit user confirmation before moving any files.

What is the best way to declutter accumulated phase directories after a milestone closes?

Decluttering accumulated phase directories involves consolidating completed milestone phases into .planning/milestones/v{X.Y}-phases archives. This preserves project history while keeping the active planning tree clean and organized.

Does archiving phase directories require confirmation before moving files?

Yes, archiving phase directories requires explicit user confirmation before moving files. The process first generates a dry-run summary of proposed moves from .planning/phases to .planning/milestones, ensuring you approve all changes.

When do I need to consolidate phase folders into versioned milestone archives?

You need to consolidate phase folders into versioned milestone archives when .planning/phases contains historical directories tied to completed milestones. This organizes phase history into .planning/milestones/v{X.Y}-phases directories after milestone closure.

Can I preview which phase directories will be moved before archiving them?

Yes, you can preview which phase directories will be moved through a dry-run summary. This identifies completed milestones and lists all proposed file moves from .planning/phases to .planning/milestones/v{X.Y}-phases before any execution.