---

name: architecture-deepening-audit description: Find shallow modules, surface confusions, and spawn sub-agents that each design a radically different deeper interface. Files the result as a refactor RFC issue. Use when working on architecture deepening audit.

Architecture Deepening Audit

Explores the codebase like a senior engineer, notes confusions, and presents numbered deepening candidates. Then spawns 3 or more sub-agents in parallel to design competing interfaces for the chosen module. Recommends the strongest, proposes hybrids, and files the result as a refactor RFC GitHub issue ready to feed into the PRD to issues pipeline. Use monthly or after a feature surge.

What you get

• Numbered deepening candidates
• Competing interface designs
• Recommendation with rationale
• GitHub RFC issue
• Blast-radius estimate per candidate
• Migration checklist

Customize your output

• Language: agnostic
• Sub-agent count: 3, 5, 7
• Repo scope: whole repo, single package, single dir
• Excluded paths: comma list
• Issue labels: comma list
• Risk tolerance: conservative, aggressive

Example output

Three interfaces for a bloated storage layer (repository pattern, event-sourced, plain functions) plus a hybrid recommendation, filed as issue 512.

Best for

Teams doing periodic architecture reviews with AI help.

---

Note: Requires human taste at the recommendation step. High confidence.

Source: Ian Nuttall · https://www.youtube.com/watch?v=EJyuu6zlQCg Category: Engineering · Priority: P4