Brainstorm — Game Concept Ideation

Setup

1. Parse argument for genre/theme hint (roguelike, space survival, open). Resolve review mode: --review flag → production/review-mode.txt → default lean.
2. Check existing work: design/gdd/game-concept.md (resume), design/gdd/game-pillars.md (build on).
3. Run phases interactively — collaborative exploration, not silent generation. Use AskUserQuestion at key decision points.

Studio principles: withhold judgment, encourage unusual ideas, "yes and...", constraints as creative fuel, time-box phases.

Phase 1: Creative Discovery

Emotional anchors (plain text, not constrained): moment in a game that moved/thrilled you, fantasy never quite found.

Taste profile: 3 most-played games (plain text — no preset options), genres loved/avoided.

Practical constraints (single multi-tab AskUserQuestion):

• Tab "Experience": Challenge & Mastery / Story & Discovery / Expression & Creativity / Relaxation & Flow
• Tab "Timeline": Weeks / Months / 1-2 years / Multi-year
• Tab "Dev level": First game / Shipped before / Professional background

Synthesize into Creative Brief (3-5 sentences: emotional goals, taste, constraints). Read back and confirm.

Phase 2: Concept Generation

Generate 3 concepts using ideation techniques:

Technique	Approach
Verb-First	Core player verb (build/fight/explore/solve) → build outward
Mashup	Genre A + Theme B tension creates unique hook
MDA Backward	Target emotion → dynamics → mechanics

Per concept present: Working Title, Elevator Pitch (1-2 sentences), Core Verb, Core Fantasy, Unique Hook ("Like X, AND ALSO Y"), Primary MDA Aesthetic, Estimated Scope, Why It Could Work, Biggest Risk.

Present all three → AskUserQuestion plain list (NO tabs): pick one, combine, or fresh directions.

Phase 3: Core Loop Design

For chosen concept, structured questioning:

Loop	Focus
30-second	Core action feel (AskUserQuestion with concept-derived options), key design dimension
5-minute	What structures cycles, "one more turn" psychology, choices
Session (30-120 min)	Complete session shape, stopping points, between-session hook
Progression (days/weeks)	Growth type (power/knowledge/options/story), long-term goal, "done" condition

Player motivation (SDT): autonomy (meaningful choice), competence (skill growth), relatedness (connection).

Phase 4: Pillars and Boundaries

Define 3-5 pillars: name + one-sentence definition + design test ("If debating X vs Y, this pillar says choose __"). Pillars should create tension with each other.

3+ anti-pillars: "We will NOT do [thing] because it would compromise [pillar]."

Pillar confirmation via AskUserQuestion → iterate until user selects "Lock these in."

→ Read references/review-mode-gates.md for review mode gate details (Phase 4 + Phase 6)

Phase 5: Player Type Validation

Using Bartle taxonomy + Quantic Foundry: primary player type, secondary appeal, who this is NOT for, market validation (successful games serving similar type).

Phase 6: Scope and Feasibility

• Platform: AskUserQuestion (PC / Mobile / Console / Web / Multiple)
• Engine: AskUserQuestion (Unity / Unreal / No preference → once decided, /scaffold-unity for Unity or /ue-project-context for Unreal). Don't second-guess if they pick one.
• Art pipeline, content scope, MVP definition, biggest risks, scope tiers

Document Generation

Generate game concept using template at .claude/skills/_templates/game-concept.md. Include Visual Identity Anchor section. Scope consistency rule: Estimated Scope must match full-vision timeline.

AskUserQuestion for write approval → if "revise" → iterate until approved → write to design/gdd/game-concept.md.

Next Steps

The pipeline's skills that ship with other profiles may not be installed: check .claude/skills/<name>/ first, and if it is missing offer /arcane-add <name> instead of running it.

→ Read references/next-steps-pipeline.md for the full 11-step pipeline after concept creation

Context Window

If context ≥70%: note that design/gdd/game-concept.md is saved, suggest fresh session.

Verdict: COMPLETE — game concept created and handed off.