hybrid-prototype

## Overview This skill implements the **Discovery Phase fast lane** as described in `docs/framework/hybrid-workflow.md`. It is intentionally lightweight: no formal GDD, no architecture, no epic breakdown. Just build it, play it, decide. **Time budget**: 1-3 days. **Agents involved**: `creative-director`, `game-designer`, `prototyper`, `godot-specialist` (or engine equivalent). --- ## Phase 1: Concept & 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 proceeding. Examples of good questions: - "Does the combat feel responsive with 200ms input lag?" - "Is resource scarcity actually fun, or just frustrating?" - "Does the movement mechanic support the intended platforming challenges?" Bad question: "Is this game fun?" (Too broad. Narrow it down.) **Ask the user**: "The core question for this prototype is: [question]. Proceed?" --- ## Phase 2: Plan (15 minutes) Define the minimum viable prototype in 3-5 bullet points: - What is the absolute minimum code to answer the question? - What can be hardcoded / placeholder / skipped? - What is the success criteria? (e.g., "Player can complete 3 jumps in a row without dying") **Present the plan to the user and ask for confirmation.** --- ## Phase 3: Build (1-2 days) **Ask**: "May I create the prototype directory at `prototypes/[concept-name]/` and begin implementation?" If yes, create the di...