QUBU / WORKSHOP

Free Game Design Document Template & GDD Builder

TOOLS
QUBU TOOL / GDD

From an idea to a testable design document

Define the rules, limits and test plan for your first playable slice in one document. Start with your own idea or load the filled tactical-puzzle example.

Fields stay in this tab and are not sent to the server. Download before closing; there is no automatic saving.

QUBU educational example: a fictional project, not an announced game or a completed player test.

Give the document an identifiable name and draft version.

State what the first playable slice includes and explicitly excludes.

Describe the player’s decision and intended experience in one sentence.

Write the player action, system response and win/loss evaluation order.

Specify unlocks, saved state and what happens after a restart.

Currency is optional: moves, time and energy can also be limited resources.

Explain what the player sees and can do in each state.

Separate the hypothesis, observation method and resulting decision. Never present an unrun test as evidence.

Test and delivery details (optional)

Event name, useful properties and the question it supports. Instrumentation is optional.

Use starting condition → action → expected result.

Observable conditions that must pass before calling the slice complete.

Fill the fields or load the example.

How to use the GDD builder

  1. Bound the first playable slice. In genre and platform, include what this version contains and which features are postponed. A target device alone does not define a shared scope.
  2. Describe one turn in order. Write what the system does after the player acts and when it evaluates winning or losing. “A fun combat system” is not an implementation rule.
  3. Make decisions testable. Open test and delivery details and specify the starting condition, action and expected result. Unresolved fields appear as [To decide] in the output.
  4. Generate, review and download. Rebuild after changing fields, or edit the output text directly. If both fields and output change, the builder asks which version to use.

Filled example: a three-level tactical puzzle

This is a fictional QUBU teaching example, not an announced game or a completed test report. It defines an offline, single-player first slice for Windows PC: a 5×5 grid, three levels, one enemy type and eight moves.

The important decision is what happens when the player reaches the exit and collides with an enemy on the final move: collision is checked first, so the player loses. This small detail turns an idea list into an actionable specification. A developer gets the evaluation order; a tester gets an expected outcome. “Load filled example” populates every field with these rules.

Download example TXT · Download example Markdown

Which download format should you choose?

TXT is a plain working copy that opens in a text editor. Markdown (.md) preserves heading markers for version control or a Markdown-compatible knowledge base. Both are editable UTF-8 text, not PDF or Word files. Downloaded documents cannot be imported back into this builder.

When should the document change?

Update the relevant test whenever a rule changes. For example, allowing diagonal movement changes both the core loop and the invalid-move test. Download a copy with a new version number and note why the previous decision changed at the end of the document. Never write a planned player test as a completed result: separate the hypothesis, observation plan and eventual findings.

For the broader method, read the GDD guide and worked example. To turn scope into team, time and budget assumptions, use the production planner. Explore other QUBU tools.