What problem does it solve? Large game design documents (GDDs, PRDs, feature lists) often contain dozens of features that cannot realistically be built in one session, causing scope explosion and incomplete deliveries. This Skill reads all design documents, identifies the core gameplay loop, and produces a focused multi-session build plan. ## Core Features & Use Cases - Document Analysis: Reads all Markdown, text, JSON, YAML, and image files in a docs folder to extract every feature, screen, entity, system, and asset. - Core Loop Identification: Separates the essential gameplay mechanic from deferrable features like shops, PvP, guilds, and leaderboards using classification heuristics. - Session Scoping: Produces a SESSION_PLAN.md with per-session file manifests, asset mappings, technical decisions, and testable success criteria, capped at 12-15 scripts per session. - Use Case: Given a folder with four design docs describing a heist game with city maps, puzzles, shops, and PvP raids, the Skill outputs a five-session plan where Session 1 builds only the city map and building tap mechanic. ## Quick Start Distill the design documents in my docs folder into a scoped session build plan for my Godot game.
