Game Design Document
The authoritative specification for a game — systems, mechanics, narrative, and art direction — binding design decisions into a coherent product reference.
A game design document (GDD) is the single source of truth for what a game is, how it plays, and what gets built. At its core it covers systems design (how mechanics interact), level design (spaces and encounters), narrative (story, dialogue, arc), and production rules (who owns decisions, what ships when).
In practice, GDDs drift. The original vision doc written before production starts is never the same document that describes the shipped game. Changes accumulate as the team discovers what works through iteration. The problem is that without version control, you lose the ability to trace why a decision was made, compare two proposed changes, or revert a system that stopped working after a balance pass.
How it works in Gameframe
In Gameframe, a GDD is a first-class versioned document. Every save creates a version. Every proposed change happens in a branch, reviewed as a merge request, and merged only when the team signs off. The canonical document is always the main branch — no “final_v3_ACTUAL.docx” naming games.
Gameframe’s Specialist Reviews read your GDD through the eyes of a Game Designer, QA Tester, Level Designer, Narrative Designer, and eight other specialists. Findings land line-anchored to the section that triggered them.
Explore GDD templates to start from a proven structure, or import an existing doc by uploading a file (Markdown, Word, PDF) or pasting a public URL.