bootstraplisted

Respond in the user's preferred language (detect from their recent messages, or fall back to the language setting in CLAUDE.md). Take a high-level game vision and turn it into a structured, executable project — decomposing pillars into epics, then driving each through the qq pipeline. Arguments: $ARGUMENTS (a description, a file path to a pitch/checklist document, or empty for interactive) ## Phase 1: Understand the Vision Read the input. Extract: - **Pillars** — the 3-5 non-negotiable design pillars (e.g., "turn-based PVP", "simple multiplayer", "WWII theme") - **Fragment rules** — specific details mentioned in passing (unit types, reference games, feel descriptions) - **Reference games** — any games mentioned as inspiration Then **ask about gaps**, using these preset directions (ask only what's missing, skip what's already covered): 1. **Target experience** — "What should 10 minutes of gameplay feel like?" (if not clear from input) 2. **Scope** — "Is this a full game or a playable demo/prototype? How many sessions to reach 'done'?" 3. **Platform & tech** — engine, target platform, multiplayer architecture (if not obvious from project context) 4. **Art direction** — placeholder/greybox or specific style? (if relevant) 5. **Hard constraints** — budget, timeline, team size, must-use systems Max 5 questions total. Make reasonable assumptions for non-critical unknowns. ## Phase 2: Decompose into Epics Break the vision into **epics** — each a self-contained vertical sli