prototype

To validate a game mechanic quickly, define a single core question and build a timeboxed throwaway prototype to test it. This approach uses intentionally relaxed code standards to measure feel and viability within 1 to 3 days of effort.

A game prototype report should include your core hypothesis, measured observations, metrics, and an evidence-based recommendation. This structure helps you decide whether to proceed, pivot, or kill a concept based on validated results.

Yes, throwaway prototyping is designed for early-stage ideation, mechanic feel checks, and timeboxed proofs of viability. It enforces a non-production code policy to ensure effort targets what matters most for validation without refactoring overhead.

Game prototyping workflow gating optionally routes full reports through a creative director review task to align outcomes with game pillars. Review mode is selected from arguments or configuration files to enforce this validation gate.

Timeboxing scope to 1-3 days effort improves game prototyping by restricting development to a single core question using minimal scaffolding. This prevents over-investment in unproven concepts and accelerates the decision to proceed or pivot.

Throwaway prototypes use intentionally relaxed standards with no production refactors and minimal scaffolding, meaning the generated code is not suitable for final production. They serve strictly to validate mechanic feel and viability rather than building architecture.