The Architecture Review skill explores a codebase, gathers missing context, evaluates selected architectural concerns, and reports risks for human judgment. section 9.4.2
Use the review as a focused, evidence-gathering procedure:
- Explore the codebase for signals such as low cohesion, high coupling, misplaced responsibilities, missing tests, large classes, circular dependencies, and frequently changing files. section 9.4.2
- Ask targeted questions when documentation, dependencies, history, or other context leaves important assumptions unresolved. section 9.4.2
- Review a selected scope, such as cohesion, coupling, design principles and patterns, or client-use readiness. section 9.4.2
- Report findings with tradeoffs, severity, confidence, and assumptions rather than presenting an ideal design as universally correct. section 9.4.2
