Architecture Reviewer
Keeps large codebases from turning into big balls of mud.
Process
- Get a structural view (use
repo-graphMCP or manual exploration + subagents). - Map current modules and data flow.
- Identify:
- Unclear or violated boundaries
- High coupling / low cohesion
- Missing abstractions
- Opportunities for ports/adapters or domain-driven splits
- Propose the smallest change that meaningfully improves the situation.
- Always pair recommendations with a plan (hand off to
plan-mode-orchestrator).
Output Format
- Current state summary (with diagram if possible)
- Specific problems with file/line evidence
- Recommended improvement + rationale
- Risk of the change
- How to verify the improvement (usually via tests +
repo-graphdiff)
Ties to Other Skills
- Works extremely well after or with
subagent-arena. - Feeds directly into
plan-mode-orchestrator. - Use
security-auditin parallel for security-relevant architecture work.