# Game Bible template

Game:
Current stage:
Next decision or check:

## Vision and Scope
- Player promise, intended audience, and platforms:
- First playable milestone and release scope:
- Open decisions:

## Game Design Document
- Player loop and intended experience:
- For each mechanic: input, rule, feedback, success, failure, and recovery:
- Rough scene roadmap and dependencies:
- Open design decisions:

## Engine and Assets
- Engine and launch instructions:
- Maps, characters, objects, interface, art, and sound:
- Asset locations and readiness:

## Development Sandbox
- Launch link or command:
- Scenario, initial state, player action, and expected behavior:
- Record build, platform, observed result, and evidence:
- Open failures and next checks:

## Scene Scripts and Playtests
- For each scene: entry, player objective, actions, dialogue, outcomes, and transitions:
- Mechanics and assets used:
- Playtest criteria, observations, fixes, and result:

## Player Manual and Wiki
- In-game How to Play outline:
- Wiki topics and screenshots:
- Published references:

## Release Pricing and Marketing
- Release scope, delivery platform, price, and payment:
- Readiness checks and release evidence:
- Store copy, screenshots, pitch scripts, and distribution links:

## Contributor Training
- Setup, first task, and verification instructions:
- Decisions and references a contributor needs:

## Updates and DLC
- Proposed changes, affected players, and release approach:
- Sandbox, scene, and compatibility checks:
- Manual, wiki, and release note updates:

## Intake and Feedback
- Who we want to hear from, including prospects, current players, and customers:
- Where feedback comes in and how we ask for it:
- Who reads each channel, replies, and follows up:
- What people said or did, with the source, date, and context:
- What came up repeatedly, what needs attention now, and what needs another conversation:
- What evidence goes back to Chapter 1, what we’ll change, and how we’ll check it: