unikit-gd-review

# Game Design — Quality Review Answer **"is this design good?"** — expert judgment on a finished design document, delivered as a severity-graded verdict with evidence. This is the design-side mirror of `unikit-review`. It is distinct from `unikit-gd-verify`, which answers the cheaper, binary **"is the design consistent with itself?"** — a review finding *can* be declined; a verify conflict cannot. The review **ends in a handoff, not a hand-list**: the full report prints to the screen, every finding is triaged into an **apply-ready** bucket (a named entailed fix to apply now) or a **research** bucket (an open question to work out), and the user makes one move — `review → [explore] → apply` — instead of routing findings one at a time into owner skills. The triage engine (the ENTAILED criterion + the interview) is shared with `unikit-gd-verify` and lives in `gd-critique` → Handoff Engine. Review is **axis-aware**: it judges **systems** (the A–K GDD), **flows** (`FLOW.md` + the `## Flow Map [gen]` / `## Funnel [gen]` renders), and **content types** (`CONTENT-TYPE.md` + the `## Content Map [gen]` render). The flow lenses — pacing / guidance / funnel — and the content lenses — schema-coherence / catalog-scale / content-fantasy-delivery — live in `references/lenses.md` alongside the system lenses. A review is most honest in a **fresh session** — the reviewer should not be the author of the document. This skill never authors or edits design **content**, and it **never writes a `d...