prune-completed-docs

Documentation pruning audits docs/plans, docs/decisions, and memory files to archive or delete completed and superseded items, reducing repository sprawl while preserving essential project history.

Reducing memory file sprawl requires auditing MEMORY.md and CLAUDE notes to classify items as active, completed, or superseded, then archiving stale entries to reclaim signal and reduce memory consumption.

Yes, safe deletion requires an archival policy with rollback capability, ensuring completed design docs are archived rather than permanently destroyed so essential history remains preserved and recoverable.

Archiving superseded decisions involves inventorying docs/decisions, classifying items no longer relevant, and applying a safe archival policy with rollback capability to maintain a clean and accurate knowledge base.

You should avoid documentation cleanup when your repository lacks a safe deletion and archival policy with rollback capability, as permanently removing completed docs without archiving risks losing essential project history.