AI Prompts for a Game Design Document: Make a One-Page GDD

Published 2026-10-15 · 2 min read · by AgentKit Co

A game design document (GDD) has a reputation for being a 60-page monster nobody reads. For a game jam, a solo project or a first game, you want the opposite: one page that answers what the game is, what the player does, and what you will actually build.

AI can help you write that page faster. It can ask the questions you forgot, propose options, and cut features when your list outgrows your calendar. It cannot decide what is fun. That part is yours.

The one-page GDD template

Copy this skeleton into any document:

TITLE:
LOGLINE (one sentence):
TARGET PLAYER:
CORE LOOP: action -> feedback -> reward/consequence -> reason to repeat
3 KEY FEATURES:
ART STYLE (one sentence, achievable with my skills):
WHAT MAKES IT DIFFERENT:
SMALLEST PLAYABLE VERSION:
MUST-HAVE / NICE-TO-HAVE / CUT:
BIGGEST RISK:

Now let us fill it with prompts. Replace the [BRACKETS] and paste into any chat assistant. If you have not given the assistant your constraints, start with a short brief: engine, hours available, team size and skills. Without constraints, AI happily proposes an open-world RPG for a 48-hour jam.

1. Pitch the idea on one page

Turn this idea into a one-page pitch: [IDEA].
Include: 3 title options, a one-sentence logline, the target player, the core loop, 3 key features, an art style in one sentence that's achievable with [MY ART SKILLS / ASSETS], what makes it different, and the smallest playable version.

Read the three title options and the "smallest playable version" line first. If that smallest version still sounds too big, say so and ask for a smaller one.

2. Find the core loop

If you cannot say what the player does minute to minute, you do not have a design yet.

Here's my game idea: [IDEA].
Describe its core loop as: player action → feedback → reward or consequence → reason to do it again.
Then suggest 3 alternative core loops for the same idea, and tell me which one is quickest to prototype as a grey-box (no art) in one day.

Ask for the version you could grey-box in a single day. A prototype with boxes and no art that is still fun is a very good sign.

3. Write a short spec for your main mechanic

Vague mechanics become bugs. A short spec forces you to decide edge cases before you code them.

Write a short spec for the [MECHANIC] in my [GENRE] game. Include:
- Player input (keys/buttons) and what happens on screen
- Rules and edge cases (what if it's used mid-air, during another action, against a wall?)
- Variables I'll want to tune, with starting values clearly marked as guesses
- Feedback: sound, visual and feel
- How it interacts with [OTHER MECHANIC]

Treat every starting value as a guess to tune while playtesting. The spec exists to make you think, not to be correct.

4. Cut the scope to fit your time

Every jam team makes the same mistake: the feature list grows and the deadline does not.

Here's my feature list: [FEATURES]. I have [HOURS] in total.
Be ruthless:
1. Estimate rough hours per feature. Label them as guesses.
2. Mark each feature as core-to-the-fun or nice-to-have.
3. Cut until the total fits with 25% of the time left as buffer.
4. Suggest cheap substitutes for expensive features (e.g. text boxes instead of cutscenes, one looping track instead of a soundtrack).

Notice the suggestion of cheap substitutes, such as text boxes instead of cutscenes. Players forgive simple presentation far more readily than a game that was never finished.

Using AI well in design work

• Keep ideas original. Ask for options and combinations, but make the final creative decisions yourself and avoid copying characters, worlds or names from other games.
• Label numbers as estimates. Hours, stats and balance values from an AI are guesses until you test them.
• Check your jam's rules about AI use for ideas and assets before you start. They differ from jam to jam.
• Finish small. A tiny finished game teaches more than a huge abandoned one.

Go further

These four prompts come from the first sections of the Prompt Pack for Game Design and Modding, which continues through level design, narrative, balancing, playtesting and shipping. You can also browse more free prompts in the prompt library. If you are preparing for a jam, our guide on game jam AI prompts covers the first critical hours.

Keep reading