project-maintenancelisted

Archive completed plans, deduplicate stale memory, and clean auto-memory at the end of a project. Use when the user wants to wrap up a plan, clean up files, or run a memory cleanup pass.
Git-Fg/taches-principled · ★ 0 · AI & Automation · score 76

Install: claude install-skill Git-Fg/taches-principled

## Routing Guidance - AFTER plan-lifecycle EXECUTE mode completes and `SUMMARY.md` is created (PLAN-ARCHIVE). - On long-running VPS instances (30+ days) when memory files have accumulated (MEMORY-AUDIT, MEMORY-DEDUP, MEMORY-CLEAN). - When the user wants to preserve plan artifacts before starting fresh (PLAN-ARCHIVE). - When stale memory entries reference deleted projects or agents (MEMORY-ARCHIVE, MEMORY-CLEAN). - Do NOT use for ongoing plans (no `SUMMARY.md` yet) — plan-lifecycle EXECUTE mode first. - Do NOT use for auditing rules files — use `rules-orchestration` AUDIT mode. - Do NOT use for capturing general session insights — use `refine` MEMORIZE. ## What This Skill Changes **Default behavior:** completed plans linger in `.principled/plans/phases/`, memory files in `~/.claude/projects/*/memory/` and `~/.claude/agent-memory/` accumulate duplicates and stale entries. The next planning cycle inherits bloated context and the next session loads noise. **With this skill:** closure work is a first-class step. Plans ship to `.principled/attic/` with learnings distilled into `.principled/memory/learnings.md`; memory files are deduplicated, stale entries archived, and the next cycle starts clean. Destructive operations default to a dry-run report; the agent then waits for explicit user confirmation before applying any change. **Why it matters:** archive-preserve-distill is the only step that converts ephemeral execution into durable knowledge. Without it, every plan rediscove