gsd-cleanup

Archive completed milestone phase directories into versioned milestone folders.

1|Updated Sep 6, 2015
One-click install
npx skills add https://github.com/deerawan/dotfiles --skill gsd-cleanup-deerawan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-cleanup
Source: https://github.com/deerawan/dotfiles/tree/main/claude/skills/gsd-cleanup
Command: npx skills add https://github.com/deerawan/dotfiles --skill gsd-cleanup-deerawan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you keep your planning workspace clean by archiving phase directories that are no longer needed after milestones are completed.

Core Features & Use Cases

  • Milestone-aware archiving: Detects completed milestones and archives their accumulated phase directories into the versioned milestones phases location.
  • Dry-run summary first: Produces a preview of what will be archived before making changes.
  • Confirmation-based execution: Archives only after you explicitly confirm.

Quick Start

Use the gsd-cleanup skill to archive .planning/phases/ phase directories from completed milestones into .planning/milestones/v{X.Y}-phases/.

Frequently Asked Questions about gsd-cleanup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I archive old phase folders after completing project milestones?

Archiving phase directories after milestones involves moving completed phase folders from `.planning/phases/` into versioned `.planning/milestones/v{X.Y}-phases/` locations. This process keeps your planning workspace clean and preserves historical phase data for future reference.

Can I preview what gets archived before running a directory cleanup?

Yes, you can generate a dry-run summary to preview exactly which phase directories from completed milestones will be archived. This allows you to verify the cleanup targets before making any actual changes to your planning folders.

How does milestone-aware archiving work for planning directory management?

Milestone-aware archiving detects completed milestones and automatically targets their accumulated phase directories for archiving. It moves these phase folders into `.planning/milestones/v{X.Y}-phases/`, ensuring only historical phase data from finished work is removed from the active planning area.

Does phase directory archiving require explicit confirmation before executing?

Yes, phase directory archiving requires explicit confirmation before executing. The workflow produces a dry-run summary of what will be archived and only proceeds to move the phase directories into the milestones folder after you provide confirmation.

When should I clean up phase directories in my planning workflow?

You should clean up phase directories whenever your `.planning/phases/` directory contains historical phase data from completed milestones. Archiving these old phase folders prevents workspace clutter and organizes past milestone data into versioned folders.