architecture-audit

# Architecture Audit $ARGUMENTS Explore a codebase organically, surface architectural friction, and propose module-deepening refactors as GitHub issue RFCs. ## Usage ``` /architecture-audit [area to audit or 'full codebase'] ``` ## What This Command Does 1. **Explores** codebase organically — friction IS the signal 2. **Presents** deepening candidates to user 3. **Frames** problem space for chosen candidate 4. **Spawns** 3+ parallel sub-agents for radically different interface designs 5. **Compares** and recommends 6. **Files** RFC as GitHub issue ## Key Concept A **deep module** (Ousterhout) has a small interface hiding a large implementation. Deep modules enhance testability, AI navigation, and enable boundary testing. A **shallow module** has a large interface with thin implementation — avoid. ## Process ### 1. Organic Exploration Use Agent (subagent_type=Explore) to navigate the codebase naturally. Note friction: - Where does understanding one concept require bouncing between many small files? - Where are modules so shallow the interface is nearly as complex as the implementation? - Where have pure functions been extracted just for testability but real bugs hide in how they're called? - Where do tightly-coupled modules create integration risk in the seams? - What is untested or hard to test? ### 2. Present Candidates Numbered list. For each candidate show: | Field | Content | |-------|---------| | Cluster | Which modules/concepts are involved | | Why coupl...