architecture-reviewlisted

# Architecture Review Skill Finds code that is hard to change and proposes a smaller-interface, bigger- implementation redesign. This is a judgment skill — no paired hook, same posture as `research-mode` in `skill-hook-pairing.md`. ## Before running Read `references/deep-module-lens.md`. It is the classification lens the review applies to every module it looks at — do not improvise a different one. ## Scope check (do this first) This lens is for software modules with interfaces: Python/shell scripts, plugin code, MCP servers. It does NOT fit markdown rules, canonical files, or prose content — those don't have "interfaces" in the Ousterhout sense. If the founder names a target that's mostly `.md`, say so and ask them to narrow to a code directory. ## Process 1. **Explore.** Spawn an `Agent` with `subagent_type: Explore` over the target directory. Ask it to walk the code and report, per file/module: what it does, its public surface (functions/classes/CLI flags other code calls), and its internal complexity. Don't apply the lens yet — just gather the shape. 2. **Classify with the lens.** For each module the Explore pass surfaced, run the questions in `references/deep-module-lens.md`. Flag only modules that are genuinely shallow (interface complexity close to implementation complexity) — a small module with a small interface is fine, not a finding. 3. **Propose, don't prescribe.** For each real finding, sketch 1-2 concrete redesigns using the voc