Product Review

Most critique fails by answering at the wrong altitude — polishing typography on a screen whose concept is wrong. And code drifts from intent in a thousand small surrenders — a state skipped, a label improvised — invisible until they compound into "why doesn't this feel right?" One skill, two modes, one method: audit top-down against the record, locate the highest broken layer, and either route it (critique) or gate the ship (QA). It diagnoses and routes; it does not fix in place, and it does not build wireframes (that is product-concept).

Part of the product-define suite. Reads the full design/ record when present. QA additionally runs the active craft skill's checklist. Findings append to validation.md; debt to decisions.md. Output format: assets/review-format.md.

Quick Reference

Core Principles

1. Diagnose top-down, stop at first failure — layer order in review-format.md.

2. Evidence per diagnosis.