explore

## Overview This skill is the **pre-workflow exploration lane**. Use it when you have one or more rough game ideas and want to validate them before choosing between the Hybrid workflow (lean, iterative) or the Full OCGS workflow (formal, structured). **When to use `/explore`:** - You have 2-4 rough ideas and want to feel them out before committing - You are not sure if your concept is fun, feasible, or scoped correctly - You want to avoid formal process overhead until you know what you're making **When NOT to use `/explore`:** - You already know your game and are ready to build → use `/start` directly - You are in the middle of production → use `/prototype` or `/hybrid-prototype` - You need a formal vertical slice → use `/prototype` within the full workflow **Key properties:** - **No workflow commitment**: Does not create `production/stage.txt`, `production/review-mode.txt`, or any production artifacts - **No process overhead**: No GDDs, no ADRs, no architecture, no sprint plans - **Time-boxed**: 1-2 days per idea maximum - **Isolated**: All work lives in `prototypes/explore/[idea-name]/` - **Composable**: Run it multiple times for multiple ideas, then compare results **Agents involved**: `prototyper` only. No director reviews, no multi-tier coordination. --- ## Phase 1: Define the Question (5 minutes) Read the concept description from the argument. State the **one core question** this prototype must answer. If the concept is vague, ask the user to clarify before proc...