brainstorm

When this skill is invoked: 1. **Parse the argument** for an optional genre/theme hint (e.g., `roguelike`, `space survival`, `cozy farming`). If `open` or no argument, start from scratch. Also resolve the review mode (once, store for all gate spawns this run): 1. If `--review [full|lean|solo]` was passed → use that 2. Else read `production/review-mode.txt` → use that value 3. Else → default to `lean` See `.claude/docs/director-gates.md` for the full check pattern. 2. **Check for existing concept work**: - Read `design/gdd/game-concept.md` if it exists (resume, don't restart) - Read `design/gdd/game-pillars.md` if it exists (build on established pillars) 3. **Run through ideation phases** interactively, asking the user questions at each phase. Do NOT generate everything silently — the goal is **collaborative exploration** where the AI acts as a creative facilitator, not a replacement for the human's vision. **Use `AskUserQuestion`** at key decision points throughout brainstorming: - Constrained taste questions (genre preferences, scope, team size) - Concept selection ("Which 2-3 concepts resonate?") after presenting options - Direction choices ("Develop further, explore more, or prototype?") - Pillar ranking after concepts are refined Write full creative analysis in conversation text first, then use `AskUserQuestion` to capture the decision with concise labels. Professional studio brainstorming principles to follow...