hybrid-prototype

Game prototyping validates a core mechanic by building a timeboxed, playable discovery prototype instead of a full GDD. You define one narrow question, create an isolated prototype, and use playtest feedback to decide whether to iterate, pivot, or kill the concept.

The best way to run rapid iteration cycles is to isolate the prototype in its own directory and continuously playtest against a single design question. This narrow loop converts feedback into actionable evidence, ensuring fast validation before committing to broader production design work.

To decide whether to pivot or kill an experimental game feature, generate a DECISION.md artifact after playtesting. This verdict file structurally evaluates the prototype evidence and selects the next step: ITERATE, PIVOT, PRODUCTIONIZE, or KILL the concept entirely.

Workflow isolation tests game prototyping concepts independently by creating a dedicated prototypes directory. This strict separation ensures each timeboxed build addresses only its specific core question, preventing scope bleed and keeping playtest feedback focused on that single mechanic.

You need a timeboxed discovery prototype instead of full production planning when facing early-stage design uncertainty. If you need fast evidence regarding input timing or mechanic responsiveness within days, a playable prototype answers the core question more efficiently than upfront planning.

A 1-3 day playable prototype is limited to answering a single, narrow design question rather than validating comprehensive game systems. It intentionally skips heavy upfront planning to test core feel and responsiveness, making it unsuitable for resolving complex architectural or narrative dependencies.