Review

Run this after every feature, before moving on. It reports issues — it does not fix them. The developer decides what matters.

Step 1 — Understand What Should Have Been Built

Read in this order:

1. The spec file from context/specs/ for the feature being reviewed
2. Any relevant context files: context/architecture.md, context/code-standards.md, context/ui-registry.md

If no spec file exists, ask the developer to describe what the feature was supposed to do before reviewing.

Step 2 — Discover What Changed

Run git diff main...HEAD --name-only to identify all files changed in this feature branch. Read each changed file.

Step 3 — Review in Three Layers