What problem does it solve? Architecture documents often look complete while hiding real gaps: decisions pasted inline instead of recorded as ADRs, NFR targets restated without realizing mechanisms, or diagrams that disagree with the prose. This Skill acts as an independent acceptance gate that judges a finished whole-system architecture document and its linked ADR files against a fixed 10-condition bar, so engineers can trust the doc before building within it. ## Core Features & Use Cases - 10-condition quality checklist: Judges boundary and external dependencies, component structure at whole-system altitude, diagram-narrative sync, the ADR mechanism (linked, immutable, one decision per file), traced and justified decisions, NFR realization, cross-cutting concerns, ASR coverage, and no fabricated claims. - Machine-parseable verdict: Emits exactly VERDICT: approve or VERDICT: revise plus actionable findings naming the failed condition, location, and concrete fix. - Delta-scoped amend reviews: Reviews only the changed decisions and their ripple when handed a change request against an approved doc, without re-judging the unchanged architecture. - Use Case: After authoring a system architecture doc with linked ADR files, run this Skill as the review gate; it flags that the datastore decision is embedded inline instead of a linked ADR and tells the author exactly how to fix it before approval. ## Quick Start Use reviewing-architecture-doc to judge docs/architecture.md together with its linked adr/ files and give me the verdict with actionable findings.