architecture-auditlisted

## What this skill does Provides a repeatable, evidence-based framework for reviewing software architectures. It evaluates a design against quality attributes (scalability, maintainability, security, reliability, performance, operability), checks for constraint violations, and produces a prioritised list of findings with actionable recommendations. ## When to use it - User asks to "review", "audit", or "assess" an architecture, design document, or ADR. - User shares a system diagram, architecture description, or tech-stack decision and wants structured feedback. - User wants to identify risks or trade-offs in a design before committing to it. - User needs a report suitable for a design review meeting. ## Instructions 1. **Understand scope.** Clarify what is in scope (components, boundaries, interfaces) and what quality attributes matter most to the stakeholder. If not stated, default to: scalability, maintainability, security, reliability, performance, and operability. 2. **Collect evidence.** Read any provided diagrams, ADRs, documentation, or code. Note what is explicit, what is implied, and what is missing. 3. **Evaluate each quality attribute.** For each attribute in scope: - State the current approach (how the architecture addresses it). - Rate the approach: `Strong` / `Adequate` / `Weak` / `Not addressed`. - Identify specific risks or gaps. 4. **Check constraints.** Identify whether known constraints (team size, budget, compliance requirements, exist