gat-brainstorm

# Brainstorm This skill explores a game concept through open-ended designer interview. Spawn `gat-designer` for design reasoning and `gat-artist` for visual direction. Pick questions from the angle table below — follow the conversation, not a script. ## Phase 1: Resolve Mode - If argument is `discuss` → Mode: `discuss` (no files written, exploration only) - If argument is a hint or empty → Mode: `design` (produces foundational design docs and global art direction) Check whether `gat/overview/game.md`, `gat/overview/systems-index.md`, or `gat/overview/art-direction.md` already exist. If so, note them — the interview may refine or replace existing decisions instead of starting from scratch. ## Phase 2: The Interview ### Core Rules - **One question at a time.** Never batch. Wait for the answer before the next question. - **Provide a recommended answer** with each question. Explain the design reasoning. - **Prefer open-ended questions.** Let the user type free-form responses. Reserve `AskUserQuestion` (multiple-choice) for when you are presenting concrete solution options and need the user to pick one. Most of the interview should be dialogue, not forms. - **Pick angles, don't follow steps.** Use the angle table as a menu. Jump to whatever dimension is most useful next — chase what's interesting or ambiguous. - **If a question can be answered by reading existing design files, read them instead of asking.** - **Spawn `gat-designer`** when you need a design reasoni...