Skill: Prune Content

Purpose

Help the user maintain a clean codebase by identifying and archiving "expired" or obsolete content. Instead of relying solely on mechanical timestamps or "deprecated" tags, this skill prioritizes contextual relevance and user judgment, often leveraging insights from onboard-repo or project cognition.

Core Objective

Primary Goal: Safely archive project content that the user or project context identifies as obsolete, reducing cognitive load without destroying history.

Success Criteria (ALL must be met):

1. ✅ Contextually identified: Candidates selected based on user intent ("archive the v1 docs") or project analysis ("this directory is from the legacy prototype").
2. ✅ User confirmed: User explicitly approved the list of files to be archived.
3. ✅ Safely archived: Files moved to _archive/<original_path> to preserve structure and history (preferred over deletion).
4. ✅ No accidental data loss: Critical directories (.git, node_modules, src) protected from broad sweeps.