---
id:"kb-2026-00218"
title:"Game Design Document (GDD)"
schema_type:"TechArticle"
category:"game-development"
language:"en"
confidence:"high"
last_verified:"2026-05-22"
generation_method: "human_only"
ai_models:["claude-opus"]
derived_from_human_seed:true


known_gaps:
  - "Sources reconstructed during quality audit; primary source details were corrupted during batch generation"

completeness: 0.88
ai_citations:
  last_citation_check:"2026-05-22"
primary_sources:
- title: "GDC Vault"
    type: "conference"
    year: 2026
    url: "https://www.gdconf.com/"
    institution: "GDC"
secondary_sources:
  - title: "GDC Vault"
    type: "conference"
    year: 2026
    url: "https://www.gdconf.com/"
    institution: "GDC"
---

## TL;DR

A Game Design Document (GDD) is the blueprint for a video game — defining mechanics, story, art direction, technical requirements, and project scope. It serves as the single source of truth for the development team. Modern GDDs are living documents (wikis, Notion) rather than static PDFs.

## Core Explanation

GDD sections: Executive Summary (one-page pitch), Gameplay (core loop, mechanics, controls), Story/World (setting, characters, narrative arc), Art/Sound (visual style, audio direction), UI/UX (menus, HUD, flow), Technical (platform, engine, tools), Monetization (if F2P), Schedule/Milestones. Key: keep it updated. Dead GDDs (outdated, too long) waste time.

## Further Reading

- [undefined](undefined)