What problem does it solve? Game designers hand over rough minigame ideas that lack concrete numbers, network authority rules, and edge-case handling, forcing developers to stop mid-implementation to ask clarifying questions. This Skill turns a raw game description into a complete, agreed specification in docs/minigames/ that tickets can be cut from without further questions. ## Core Features & Use Cases - Core Reuse Audit: Classifies every mechanic as already in Core, needing a Core extension, or unique to the game, preventing duplicated code across minigames. - Network Model Definition: Assigns authority and synchronization (NetworkVariable vs RPC, server-authoritative outcomes) for every state element, including disconnect handling for asymmetric roles. - Rule Gap Detection: Runs checklist questions on ranking all players, ties, 2-to-8 player scaling, timeouts, and stuck states, then resolves open questions with the user in one batch. - Use Case: A game designer drops a Markdown file describing a new asymmetric minigame; the Skill produces docs/minigames/<game>.md with sections 9-11 filled, an art brief, and status 'agreed', ready for ticket slicing via /mg-tickets. ## Quick Start Run the mg-spec skill with the path to my raw minigame description file to produce a complete agreed specification in docs/minigames/.