What problem does it solve? It prevents requirement drift at the start of GUI development by forcing interactive clarification and human approval before any code is written, turning vague panel requests into a reviewed, versioned requirements contract. ## Core Features & Use Cases - Plan Mode Requirement Gathering: Enters Claude Code plan mode to read-only explore ui_data.lua, existing panels, and injected knowledge-base pitfalls, then asks the user batched clarifying questions via AskUserQuestion. - Human Approval Gate: Writes a requirement-focused plan and blocks on ExitPlanMode approval, iterating on feedback until the user accepts; zero write operations occur before approval. - Contract Generation: After approval, initializes pipeline run state and writes a refined GUI_PLAN.md containing module split design (sub Views/Panels), per-module ViewModel data contracts, and acceptance criteria for downstream review. - Use Case: A developer says "add a batch-sell button to BagPanel"; the skill locates the prefab and ViewModel conventions, confirms open questions with the user, gets the plan approved, and hands a precise contract to the gui-draft code generation stage. ## Quick Start Ask the assistant to plan a new GUI panel by providing a panelId and requirement description, for example: run gui-plan for BagPanel to add a batch sell button.
