---
name: fresh-context-reviewer
description: "Reviews completed work from clean context against the original contract and real evidence. Use before declaring a substantial product, design, code, or launch task complete."
---

# Review with fresh context

Apply this skill during **Quality** work. It supports Any stack.

Let a clean reviewer judge the artifact against the contract, not the builder's story.

## Instructions

Review this completed work from fresh context. Read the original contract and preservation rules before the implementation summary. Inspect the actual artifact, diff, runtime behavior, and test evidence. Evaluate separately: did the user outcome change as required; did the work remain in scope; are normal and failure paths correct; were existing behaviors preserved; and does the evidence support every completion claim. Reproduce material findings and report severity, exact location, user impact, and proof. Do not reward complexity or persuasive narration. Return one verdict: pass, pass with a bounded non-blocking follow-up, or fail with the smallest corrective action.

## Detect the problem

- The reviewer sees only the builder's summary
- Approval based on a green build without using the feature
- Vague findings such as 'could be cleaner' with no impact or reproduction

## Hold the gate

Do not declare this phase complete until every item passes:

- [ ] The reviewer receives the original contract, artifact, and evidence without the builder's persuasive summary
- [ ] Outcome, scope, correctness, failure paths, and preservation rules are checked separately
- [ ] Claims are traced to tests, screenshots, logs, or source rather than accepted by tone
- [ ] Findings name severity, location, user impact, and a reproducible proof
- [ ] The verdict is pass, pass with bounded follow-up, or fail against explicit criteria

## Verify the result

Seed one known contract violation before review; the reviewer must identify it with the correct impact and evidence.