/cold-review

Run an independent review of actual work artifacts using fresh context. The goal is to surface issues the current agent misses because it has too much context, owns the work, or is biased toward its own implementation. This is a workflow, not a persistent mode.

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. cold-review's modes are the reviewer-count tiers (narrow/medium/broad → 1/2/3 reviewers); its venue is inline only (cold-review spawns its own reviewers — COP never wraps a self-orchestrating skill).

Boundary

Use cold-review for completed or in-progress work artifacts: diffs, files, code, tests, screenshots, UI states, plans, specs, docs, command outputs, worker reports. Do not use it for raw ideas. Use insight-adversarial for multi-POV critique of plans/ideas/strategy, verify for a formal self-gate, and double-check when the current agent should re-read and challenge a specific target itself.

Step 1 — Establish target and objectives

Identify: the work assessed; the objectives (infer and label as inferred if not given); the constraints (non-goals, compatibility, style, acceptance criteria, preferences); and the available evidence (tests, commands, screenshots, docs, diffs, source). If no concrete artifact exists, stop and ask for the target — do not review from vague memory.

Step 2 — Classify the work

Classify the primary target type and choose lenses accordingly: