game-planner

To turn a vague game idea into a game design document, you need a structured planning process that extracts concrete decisions through a Socratic design interview before synthesizing the results. This approach clarifies game mechanics and scope without acting prematurely.

Creating a GDD before game development prevents wasting time writing code by establishing a clear design contract. It runs phased rounds for identity, mechanics, world feel, and scope to catch design gaps early through independent auditing.

Yes, you can use this game planner for any genre because it applies scope-appropriate planning that skips irrelevant GDD sections based on your specific game type. It adapts the design interview to fit the mechanics you provide.

A Socratic design interview for game planning is a guided clarification process that asks targeted questions across phased rounds to extract concrete decisions from your concept. It enforces an ask-before-act guardrail to ensure all design elements are fully scoped.

To audit a game design document for missing mechanics or scope, run independent audit passes using tag-scoped questions. This process synthesizes your draft into a complete design contract and identifies gaps in world feel, assets, and game mechanics.

A limitation of automated game design planning is that it requires multiple phased rounds for identity, mechanics, and scope, meaning you cannot skip the Socratic interview process. It mandates thorough auditing before any design contract is finalized.