gsd-cleanup

Archive completed milestone phase directories into versioned milestone storage after user confirmation.

1|Updated May 24, 2026
One-click install
npx skills add https://github.com/tinner-deinno/innova-skills-lib --skill gsd-cleanup-tinner-deinno
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-cleanup
Source: https://github.com/tinner-deinno/innova-skills-lib/tree/main/core/gsd/gsd-cleanup
Command: npx skills add https://github.com/tinner-deinno/innova-skills-lib --skill gsd-cleanup-tinner-deinno

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of cluttered planning data by archiving accumulated phase directories from completed milestones into a clean, versioned milestones history.

Core Features & Use Cases

  • Milestone phase cleanup: Moves phase directories from .planning/phases/ into .planning/milestones/v{X.Y}-phases/ once milestones are completed.
  • Dry-run visibility: Produces a summary of what will be archived before making changes.
  • Confirmation-based execution: Performs the archive only after user confirmation to prevent accidental re-organization.

Quick Start

Tell the agent: “Run gsd-cleanup to archive completed milestone phase directories from .planning/phases/ 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 completed milestone phase directories automatically?▼

You can archive completed milestone phase directories by moving them from `.planning/phases/` into versioned milestone storage under `.planning/milestones/v{X.Y}-phases/` to keep your planning data uncluttered. The process identifies accumulated phases and requires user confirmation before archiving.

What is the best way to clean up leftover planning phase directories?▼

The best way to clean up leftover planning phase directories is to use a dry-run summary to review what will be archived, then confirm the execution to move them into versioned milestone storage. This prevents accidental re-organization of your filesystem.

Can I preview what gets archived before moving phase directories?▼

Yes, you can preview what gets archived by generating a dry-run summary that identifies accumulated phase directories from completed milestones. This summary shows exactly what will be moved into `.planning/milestones/v{X.Y}-phases/` before any changes are made.

Does milestone phase cleanup require manual confirmation before archiving?▼

Yes, milestone phase cleanup requires manual confirmation before archiving to prevent accidental re-organization. The Skill performs end-to-end identification of phase directories and produces a summary, but only archives them after you explicitly approve the action.

When should I archive phase directories into versioned milestone storage?▼

You should archive phase directories into versioned milestone storage when your `.planning/phases/` directory has leftover folders from earlier completed milestones. This applies to planning-workflow cleanups where accumulated phase directories need to be organized into `.planning/milestones/v{X.Y}-phases/`.