/critique

Advisory review of the last plan, code, architecture, or UI output. Runs four analysis passes and emits a structured report. Never blocks — advisory only.

Structured execution spec: protocol.yon. Read it for the canonical rules and step sequence; this file is explanation. The two must stay in sync — if you edit one, update the other and refresh the @STAMP date.

Caller Options. Before executing, run the Caller Options protocol (caller-options/SKILL.md): triage this invocation for material optionality across the venues and modes declared in front-matter; if one path clearly dominates, proceed silently; otherwise surface the options to the caller. A resolved-invocation marker means COP already ran — execute the fixed combination directly, do not re-enter COP.

Phase 1 — Classify

Identify what is being critiqued. Pick exactly one: Code, Plan, Architecture, UI. If the subject is ambiguous, ask for clarification before proceeding.

Phase 2 — Analysis

Run all four passes. Passes 1–3 are independent. Pass 4 depends on Risks.