What problem does it solve? A growing docs/solutions/ knowledge store accumulates contradictory lessons over time — an old "use sync exec" note sits next to a new "use async exec" note with nothing flagging the drift. This Skill runs a scoring-based refresh sweep that detects stale, duplicate, and overlapping learnings and archives the losers without ever deleting anything. ## Core Features & Use Cases - 5-vector overlap scoring: Groups solution docs by (problem_type, component) and classifies each group as Keep, Update, Consolidate, Replace, or Delete using the flywheel_memory MCP tool's refresh_learnings operation. - Rename-aware staleness detection: Runs git log --follow before classifying a component as stale, so renamed files are not falsely flagged for deletion. - Archive-only mutation with confirmation gates: Pruned entries move to docs/solutions/_archive/ via git mv (preserving history), and every Delete classification requires its own explicit AskUserQuestion confirmation. - Use Case: After months of compound-engineering work, your docs/solutions/ folder has 80 entries with contradictory advice for rewritten components. Run the sweep to get a grouped report, confirm the Consolidate/Replace actions, and archive 15 stale entries while keeping the fresh primaries. ## Quick Start Ask the agent to run a compound refresh sweep over the docs/solutions learning store and report which entries should be consolidated, replaced, or archived.
