unikit-gd-recon

# Game Design — Brownfield Reconnaissance (code → RECON.md) Reconstruct **candidate** design facts from a working codebase into one passive `RECON.md`, for the brownfield case the rest of the module cannot serve: a team with a **live game and no GDD** has nothing to import — the only source of design facts is the code itself. This skill quantises that one allowed crossing of the one-way boundary into a **read-only research verb**: it reads code, writes a single document, and **calls no one**. **This skill is honest about its limit.** Code carries *structure*, never *intent*. It yields a roster, a dependency graph, content schemas — a **skeleton**. It cannot yield pillars, the target fantasy, or the "why". A filled-but-soulless GDD is **worse** than an empty one, so every reconstructed fact is tagged `provenance: extracted from code` (held to ≥ Major on review) and everything code cannot answer goes into a mandatory **`## Intent Gap`** for a human to fill. The membrane is one-directional: **code → `RECON.md` → (ordinary import)**. Downstream, `RECON.md` is just a document. **This skill writes only `RECON.md` and invokes no skill.** It has **no `Skill` tool** — the dispatch to `/unikit-gd-spec` is a printed *recommendation*, never an inline call (the same mechanical guarantee `unikit-gd-apply` gets from owning no `Write`). **Optional seed — what the user may pass in.** Recon runs with **no argument** (scan the whole project) or with an **optional seed**: a free-text game de...