What problem does it solve? When you ask where or how to improve a codebase's architecture without naming a specific change, you get vague impressions instead of grounded findings. This Skill audits modules for shallow interfaces, coupling, and tech debt, producing ranked refactor cards backed by files and symbols actually read. ## Core Features & Use Cases - Scoped architecture audit: Audits a named path, module, or pain point, or derives scope from git churn hotspots over the last six months via scripts/hotspots.mjs. - Delegated evidence-based analysis: Dispatches a general-purpose delegate on Opus that reads the scoped code within a strict read budget and writes at most 5 ranked cards with friction, refactor, payoff, confidence, and migration cost. - Two output modes: Produces ranked cards in the reply, or in a read-only planning mode writes a full plan artifact following the planning skill's plan specification. - Use Case: Ask where the coupling problems are in your checkout flow, and receive ranked cards naming exact files and symbols, each with the interface the refactor leaves and its migration cost. ## Quick Start Ask the assistant to run the deepen skill on the payments module to find the refactors that would give it a smaller interface over its implementation.