What problem does it solve? Game developers often invest weeks writing GDDs and production code for concepts that turn out not to be fun. This Skill validates whether a core game idea is worth designing by producing a fast, throwaway prototype and a clear PROCEED/PIVOT/KILL verdict before any design documentation is written. ## Core Features & Use Cases - Falsifiable Hypothesis Framing: Forces the concept into a testable question and targets the riskiest assumption first, stopping early if the concept is too vague to test. - Three Prototype Paths: Routes to HTML (browser-playable, no install), Engine (native feel validation for action games), or Paper (rules document plus play log) based on genre and what the hypothesis actually tests. - Structured Verdict Workflow: Runs a playtest debrief, generates a REPORT.md, maintains a prototypes index, PIVOT notes, and a GRAVEYARD.md for killed concepts. - Spike Mode: A ~4-hour lightweight mode for mid-production technical or mechanic questions with no phase gate implications. - Use Case: After brainstorming a grappling-hook platformer concept, run this Skill to build a minimal engine prototype testing whether players can chain three swings within two minutes, then receive a PROCEED verdict with a full report before writing any GDDs. ## Quick Start Use the prototype skill to validate my game concept by building a throwaway prototype and giving me a PROCEED, PIVOT, or KILL verdict.
