design-prune

To prune outdated design documentation without losing essential history, you can identify stale sections and deprecated patterns, then archive them while preserving essential history. This process keeps current decisions discoverable and maintains a record for compliance and auditing.

The best way to clean up legacy design docs and migration notes is to apply strategic pruning with configurable levels like conservative, normal, or aggressive. This detects outdated patterns and duplicates, updates frontmatter, and archives pruned content to balance brevity with context.

Yes, you can control how aggressively design docs are pruned by choosing conservative, normal, or aggressive pruning strategies. This balances brevity with context, allowing you to manage migration notes and evolution notes while automatically moving pruned content to archives.

Staleness scoring works by evaluating design documentation to detect outdated patterns, deprecated migration notes, and duplicated content. It generates a pruning plan that identifies historical content, allowing you to update frontmatter and archive cruft while keeping current decisions discoverable.

You do not explicitly need frontmatter to archive cruft, but the pruning process includes frontmatter updates as part of its validation. Managing cross-document references and archiving pruned content works best when design modules have structured metadata to track evolution notes.