brainstormlisted

# Brainstorm Reply in the project conversation language (CLAUDE.md → Language); code, identifiers, paths and commit messages stay in English. Reference: `stack-reference/index.md` (what the studio builds and with which versions); the brief feeds the `product-spec.md` / `game-concept.md` templates that follow. ## Phase 1: Conversation Clarify via `AskUserQuestion` (one at a time): for whom; which pain/desire; what already exists on the market (allow `WebSearch` for 3–5 comparable products); constraints (time, budget, stack, platforms); for games — genre, session, the player's "verb" (the most frequent action). ## Phase 2: Framing Generate 3 positioning variants (narrow/medium/wide scope) with cost and risk; for games — 3 core-loop variants (MDA: mechanics → dynamics → aesthetics). Propose success metrics and "what must be true" for the idea to work (hypotheses to validate). ## Phase 3: Concept brief Draft `docs/specs/concept-brief.md`: essence, personas, pain, differentiation, MVP candidate, hypotheses and how to validate them (landing page/prototype/interviews), risks, next step. "May I write it?" — one `AskUserQuestion`: write (Recommended) · show the draft/diff first · not now After the "write" answer: `touch .claude/.write-consent` (rule 7 — the consent-guard hook checks the marker). Verdict: `COMPLETE`. Next step — one `AskUserQuestion`: `/setup-stack` (Recommended) · `/product-spec` or `/game-concept` directly · revise the brief.