game-bootstraplisted

# Bootstrap a GameGen project Read [shared context](../../references/shared-context.md). Start from the actual repository and conversation. The required project file is `.agents/gamegen-prefs.json`. Never bootstrap the plugin package itself as a game. ## Resolve choices before production 1. Inspect existing preferences, project layout, accepted concepts and user decisions. Carry forward the title, description, player goal and development scope already provided. Inspect available Godot, local Blender, image-generation and optional service capabilities. For Blender, discover the executable and run the background Python probe in the [CLI workflow](../../references/blender-cli.md); no Blender MCP setup is needed. Reuse working connections for providers that use them. 2. If the file is absent, run `python3 <plugin-root>/scripts/prefs.py init --project <game-repository>`. This writes an unconfirmed draft, not approved defaults. Use `read` for an existing file and preserve its chosen paths. 3. Run `questions --project <game-repository>` and use [the intake catalog](../../references/intake.json) to identify unresolved sections. Prepare one setup phase with related questions grouped into tool-sized batches. Ask all relevant production choices during this phase, before asset or gameplay production. 4. Use the available ask-question tools. In Default mode use the asynchronous question tool when available; use a blocking question tool only in a mode that suppor