What problem does it solve? Before hi-fi design and UI engineering begin, someone must decide whether a finished wireframes document is actually buildable — every flow-named screen and state covered, layouts unambiguous, components real, and accessibility reserved. This Skill acts as that independent acceptance gate, judging a markdown wireframe against a fixed, single-sourced bar instead of subjective taste. ## Core Features & Use Cases - Fixed 15-condition checklist: Judges screen coverage, per-screen states (empty/loading/error/success), layout clarity, component consistency, affordance annotation, microcopy, responsive behavior, screen-composition accessibility, and fidelity scope. - Machine-parseable verdict: Emits exactly one line — VERDICT: approve or VERDICT: revise — plus actionable findings naming the failed condition, location, and concrete fix. - Delta-scoped amend reviews: Reviews only the diff and its ripple effects when judging an amended document, rather than re-litigating untouched screens. - Use Case: After authoring wireframes for a checkout flow, run this reviewer with the wireframes doc plus the upstream user-flows and design-system; it returns a revise verdict with findings like a missing error state on the payment screen, which the author fixes in one pass. ## Quick Start Use reviewing-wireframes to judge the finished wireframes document at docs/specs/checkout-wireframes.md against the user-flows and design-system, and give me the verdict and findings.
