# Architecture Review

> Use when architecture is the primary review objective for boundaries, coupling, ownership, scalability, resilience, maintainability, or long-term change cost; use review for a general defect review.

- Skill: `nono911/architecture-review` (Agent Skill, multi-file: 4 files)
- Install (CLI): `npx skillmds@latest add nono911/architecture-review`
- Raw SKILL.md: https://api.skillmd.com/api/skills/nono911/architecture-review/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: nono911 (https://skillmd.com/u/nono911)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/nono911/architecture-review

---


# Architecture Review

## Purpose

Evaluate whether system structure supports the stated product and operational needs, using repository evidence rather than generic pattern scoring.

## Workspace protocol

Read `references/workspaces.md` once per agent task before selecting or creating workflow artifacts; reuse it unless repository scope or task authority changes. This skill owns only the task-specific behavior below.

## Inputs

- Goals, constraints, quality attributes, diagrams or proposals
- Current modules, dependencies, data flows, deployment topology, and ownership boundaries
- Known scale, failure modes, and change scenarios

## Outputs

- Current-state model and material architectural findings
- Tradeoff analysis with prioritized recommendations
- Explicit assumptions, residual risks, and staged options when change is warranted

## Rules

- Read `references/finding-rubric.md` before emitting defects intended for remediation; keep tradeoff advice that does not cross the finding threshold in recommendations.
- Start from desired capabilities and likely changes, not fashionable architecture.
- Trace dependency direction, state ownership, contracts, failure propagation, and operational boundaries.
- Separate structural problems from local code-quality issues.
- Quantify scale or cost claims when evidence exists; label estimates otherwise.
- Prefer incremental, reversible improvements and describe migration cost.
- Remain read-only unless implementation is explicitly requested.

## Decision-log updates

Record accepted boundaries, ownership, technology choices, quality-attribute priorities, and deliberately accepted coupling or debt. Capture alternatives and migration consequences.
When durable state is approved, append structural tradeoffs or accepted architecture risk to the selected work item's decisions.md and track actionable defects in findings.md; otherwise report them in the final response.

## Escalate to the human

Escalate when priorities conflict, ownership is unclear, a recommendation commits the team to major platform or vendor cost, or missing product and operational constraints prevent a defensible recommendation.