What problem does it solve? Full ECC installs load every skill, rule, and hook regardless of what a project actually uses, creating noisy context and stale configurations. This Skill builds an evidence-backed install plan so a repo only loads the components that match its real stack. ## Core Features & Use Cases - Evidence-Based Classification: Sorts skills, commands, rules, hooks, and extras into DAILY (always loaded) and LIBRARY (searchable on demand) buckets, with every DAILY decision citing concrete repo evidence like file extensions, lockfiles, and framework configs. - Parallel Review Passes: Splits the audit across six passes (agents, skills, commands, rules, hooks/scripts, extras) that can run as parallel subagents or sequentially. - Install Plan and Verification: Produces a DAILY inventory, LIBRARY inventory, install plan, and verification report, plus an optional skill-library router for searchable access to demoted components. - Use Case: A TypeScript/Next.js repo inherited a full ECC install including Python and Django rules. Run this Skill to demote off-stack components to LIBRARY, keep TypeScript rules in DAILY, and verify no stale hooks remain active. ## Quick Start Ask the agent to sort this repo's ECC components into DAILY and LIBRARY buckets and produce an evidence-backed install plan.