What problem does it solve? Starting a new game engine feature without a structured scoping pass leads to scope creep, missed rules requirements, and architectural violations discovered only after code is written. This Skill enforces a consistent requirements-analysis workflow before any implementation begins. ## Core Features & Use Cases - Issue-Driven Scoping: Reads a GitHub issue via gh issue view, pulls the relevant rules text with page citations, and greps the current engine state in game_engine.gd and game/. - Structured Scoping Document: Produces current state, rules requirements, proposed function signatures and data flow, open questions with recommended defaults, explicit in/out-of-PR scope boundaries, and a suggested branch name. - Architecture Guardrails: Enforces the pure-RefCounted contract for game/, dice injection conventions, JSON ruleset preferences, and Euclidean grid distance at scoping time. - Use Case: You say "let's start #42" for a new melee mechanic. The Skill reads the issue, quotes the v17 rules, reports what the engine already does, and hands you a scoping doc to approve before a branch is created. ## Quick Start Ask the assistant to scope issue 42 for the new melee mechanic and wait for the scoping document before writing any code.
