A short one helps even solo developers, because writing it exposes what is vague. Keep it to one page.

Where does the text go?

Nowhere. It stays in your browser until you copy or download it.

What goes in a one-page GDD?

The pitch in one sentence, the core loop, the player's goal, the main mechanics, the look, the target platform and what is out of scope.

Where should I keep the document?

Somewhere the team opens every day: the repository's README, a pinned note or a shared doc. A document no one opens stops being true.

One-Page Game Design Document Generator (Markdown)

A long design document is rarely read. A one-pager forces you to decide. Fill in the fields, copy the Markdown and keep it where your team can see it.

# Untitled game

## One-sentence pitch
_To do_

## Genre and references
_To do_

## Core loop
_To do_

## Target player
_To do_

## Platforms and engine
_To do_

## Art and audio style
_To do_

## Scope and release date
_To do_

## Business model and price
_To do_

## Biggest risks
_To do_

When to use it

Before a game jam
Fill the one-pager in the first hour so the whole team agrees on the core loop and the scope.
Pitching to a publisher or a friend
A single page answers the questions they ask first: what the player does, why it is fun and who it is for.
Cutting scope mid-project
Re-read the page when the project grows; anything that doesn't serve the core loop is a candidate to cut.