gat-story

# Story This skill explores and documents a game's narrative through open-ended writer interview. Spawn `gat-writer` for narrative reasoning. Spawn `gat-designer` or `gat-artist` only when story choices need design-system or visual-direction checks. 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: `story` (produces narrative docs under `gat/narrative/`) Check whether these files exist: - `gat/overview/game.md` - `gat/overview/systems-index.md` - `gat/overview/art-direction.md` - `gat/narrative/story.md` - `gat/narrative/world.md` - `gat/narrative/characters.md` - `gat/narrative/quests.md` - `gat/narrative/dialogue.md` If foundational overview docs exist, read them before asking questions that they already answer. If they are missing, proceed only with high-level narrative brainstorming and note that final narrative docs may need revision after `/gat-brainstorm` establishes the game overview and systems. ## 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 narrative reasoning. - **Prefer open-ended questions.** Let the user type free-form responses. Reserve `AskUserQuestion` for concrete options where the user needs to choose. - **Pick angles, do...