gat-designlisted

# Design This skill writes all design and art documents. ## Phase 1: Resolve Mode Check existing files: - If `design/gdd/game.md` missing → Mode: `wizard` - If argument matches a system name in `systems-index.md` → Mode: `system` - If `game.md` exists and at least one system in `systems-index.md` lacks a GDD → Mode: `continue` - If `game.md` exists and all systems have GDDs → report design is complete, stop Treat any non-system-name argument as a concept hint passed into the wizard. ## Phase 2: Wizard Skip this phase if Mode is `continue` or `system`. ### Step 1 — Core Concept If a concept hint was provided, first spawn `gat-designer` to extract what is already answered from the hint: - genre / style - core player verb - target feeling - rough scope Then use `AskUserQuestion` to ask only the questions the hint did not answer. If the hint answered all four, skip Step 1 entirely and proceed to Step 2. ### Step 2 — Concept Direction Spawn `gat-designer` to generate 2-3 short concept directions (3-5 sentences each) based on Step 1 answers. Use `AskUserQuestion`: - "Which direction resonates most, or describe your own?" - Options: present the 2-3 directions as options plus "Describe my own" ### Step 3 — System Scope Spawn `gat-designer` to propose a system list with brief rationale for each, based on the chosen direction. Use `AskUserQuestion` (multiSelect): - "Which systems should be in scope?" - List the proposed systems as options Then use a second `AskUserQ