sg-cleanup

Archive completed milestone phase directories and report a grouped summary table.

2|Updated May 15, 2026
One-click install
npx skills add https://github.com/gyuha/super-gsd --skill sg-cleanup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sg-cleanup
Source: https://github.com/gyuha/super-gsd/tree/main/skills/sg-cleanup
Command: npx skills add https://github.com/gyuha/super-gsd --skill sg-cleanup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

sg-cleanup prevents clutter and confusion in your GSD learning loop by automatically archiving completed milestone phase directories instead of leaving them scattered in the active phases area.

Core Features & Use Cases

  • Delegated archival to gsd-cleanup: Calls the gsd-cleanup Skill to perform the actual moves and commit, ensuring sg-cleanup only reports outcomes.
  • Before/after snapshot diffing: Compares .planning/phases/ before and after delegation to determine exactly which phase directories were archived.
  • Human-readable milestone summary: Renders a table grouped by milestone version showing archived phase slugs, counts, and destination paths for each archived milestone.

Quick Start

Use the sg-cleanup skill to archive accumulated completed milestone phase directories and get a table summarizing what was moved and where.

Frequently Asked Questions about sg-cleanup

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

FAQPage Schema
How do I archive completed milestone phase directories in a GSD planning workflow?

To archive completed milestone phase directories, this Skill delegates file moves to gsd-cleanup and then generates a summary table. It snapshots `.planning/phases/` before and after the run to identify exactly which phase slugs were moved into `.planning/milestones/vX.Y-phases/`.

What is the best way to clean up completed planning phases without losing track of what was archived?

The best way to track archived planning phases is using a before-and-after snapshot diff of `.planning/phases/`. This approach derives the exact archived phase slugs and groups them by milestone version into a human-readable summary table.

How does milestone management handle workspace hygiene for accumulated phase directories?

Milestone management handles workspace hygiene by archiving accumulated phase directories from completed milestones. It delegates the actual file moves to gsd-cleanup, ensuring the active phases area stays uncluttered while providing a clear diff report of the changes.

Can I use this cleanup orchestration tool if I do not have the gsd-cleanup dependency?

No, you cannot use this cleanup orchestration tool without gsd-cleanup. The Skill explicitly delegates all file moves and git commit operations to gsd-cleanup, meaning it only functions as a reporting wrapper if that dependency is available.

Does this Skill perform git commits when archiving phase directories?

No, this Skill does not perform git commits or file moves. It strictly delegates those actions to gsd-cleanup, limiting its own scope to snapshotting the `.planning/phases/` directory and rendering a summary table of the archived results.

When should I run phase directory archival for my planning cycles?

You should run phase directory archival when completed milestones leave scattered directories in `.planning/phases/`. Running it prevents clutter and confusion in your GSD learning loop by reliably moving accumulated phases into versioned milestone folders.