Specification-Compliance Review

Overview

Use this skill when an implementation is described as partial, passing, or complete and the task is to determine whether it actually satisfies an explicit specification. This is not a generic code review and not a re-run of the test suite. The central question is: does every normative requirement have both a correct implementation path and a meaningful proof?

A green build proves syntax, compilation, and perhaps the tested examples. It does not prove race behavior, cancellation semantics, exact backpressure policy, integration parity, or compliance with explicit non-goals.

Workflow

1. Establish the review baseline

Read, in order:

1. The task specification and surrounding plan/release gates.
2. Repository guidance (AGENTS.md, README, project instructions).
3. The changed files and their callers.
4. The tests added or claimed as evidence.
5. Git status/diff and recent relevant history.