What problem does it solve? Subsystems accumulate cruft over time: pass-through modules, stale names, and responsibilities that drift from their original purpose. This Skill runs a scheduled, low-frequency architectural review over one subsystem at a time and produces a report of deletion candidates, fold candidates, and interface drift — without touching any code. ## Core Features & Use Cases - Deletion test per module: For each module, asks whether deleting it would drop complexity, leave it unchanged, or spread it everywhere, classifying modules as deletion candidates, fold candidates, or load-bearing. - Interface drift detection: Flags modules whose current responsibility no longer matches their name or original purpose, proposing rename, split, or boundary fixes. - Structured report output: Writes an inventory table, verdicts, and 1–3 recommended follow-up cleanup plans to CodeLog/Architecture/architecture-pass-V{n}.md. - Use Case: Before a major refactor of the Tasks subsystem, run a quick pass to identify which of its modules are thin pass-throughs that can be folded into callers, then queue the cleanup as separate planned changes. ## Quick Start Run an architecture pass on the Tasks subsystem with a quick scope and write the report to the CodeLog.
