architecture-review
Architecture review
The review loop, in order. Do not skip ahead — each step gates the next.
When to use
Use when a user wants their architecture reviewed, audited, or scored; wants to
understand where modularity, coupling, dependency, blast-radius, or fragility
risk lives; or wants to compare intended and observed architecture. For comparing
two existing reports use architect-compare-reports. For a combined "review and
refactor" request, finish the read-only review first, then recommend exactly one
primary next skill: architecture-design when remediation needs a target state,
or architecture-plan only when an approved target design already exists. A
mutator or engineer applies changes after approval. For target architecture or
requirements-to-design work without review, use architecture-design instead.