architecture-reviewer

Review the design spec against the approved requirements and investigation notes, trace each behavior through current and target production paths, then record findings in a structured design review report. This skill applies a template covering boundaries, interfaces, dependencies, and data transitions.

A design review report is the canonical artifact recording the review basis, structural verdicts, findings, and the pass, fail, or blocked decision for a design spec. It stays updated across review rounds while a revision record tracks the chronological history.

Classify a finding as a Requirement Gap when the proposed correction would introduce new product behavior, policy, threat model, migration obligation, or operational contract not covered by approved requirements. It routes back for explicit user approval instead of being treated as a design defect.

No, not when in-scope fallback, recovery, or lifecycle machinery depends on an unsupported material premise. The premise must be validated as reachable through a product-supported trigger, removed, or routed upstream before the design can pass.

The review cannot redefine approved business decisions or invent new requirements, and it depends on complete upstream inputs like requirements docs and investigation notes. Missing evidence produces a Blocked or Unclear result rather than a judgment.