# Game Project Brief

## 1. Product decision

- Working title:
- One-sentence player promise:
- Target player and context:
- Core action repeated during play:
- Win, fail, restart, and session-end rules:
- What the first production milestone must prove:

## 2. Platform and input

- Launch platform(s):
- Operating-system or store boundary:
- Supported input devices:
- Orientation, resolution, and aspect-ratio rules:
- Minimum representative device or hardware tier:
- Accessibility requirements in scope:
- Explicitly unsupported platform or device combinations:

## 3. Game structure

- Genre and camera:
- Local, online, or hybrid mode:
- Progression and save model:
- Number and type of representative levels or sessions:
- Content creation method:
- Tutorial and first-session boundary:
- Interruption, reconnect, and return behavior:

## 4. Art, audio, and interface

- Visual direction and approved references:
- 2D, 2.5D, or 3D production path:
- Character, environment, prop, VFX, UI, and animation scope:
- Audio and localization boundaries:
- Licensed, commissioned, and reusable assets:
- Source-file and attribution requirements:

## 5. Technical boundaries

- Engine and approved version:
- Existing source, plugins, SDKs, and accounts:
- Backend or multiplayer authority:
- Analytics, ads, purchases, or platform services:
- Privacy, consent, security, and credential boundaries:
- Build environments and repository ownership:

## 6. Performance and QA evidence

- Named device or hardware matrix:
- Graphics and quality settings:
- Repeatable stress route:
- Loading, memory, frame-time, thermal, and network checks:
- Functional acceptance route:
- Severity definitions and regression rule:
- Evidence required with every candidate build:

## 7. Milestone acceptance card

Copy this card for each milestone.

- Milestone name and purpose:
- Included decisions and outputs:
- Explicit exclusions:
- Build identifier and source revision:
- Test environment and route:
- Required evidence:
- Known issues allowed at acceptance:
- Reviewer and decision owner:
- Outcome: accept / revise / stop / change scope
- Decision date and linked evidence:

## 8. Change control

- What changed and why:
- Which accepted assumption or output it affects:
- Impact on content, code, art, testing, accounts, schedule, and handover:
- Options considered:
- Approved option and owner:
- Updated milestone evidence:

## 9. Final handover

- Repository and branch map:
- Reproducible build instructions:
- Engine, packages, native plugins, and versions:
- Art, design, audio, localization, and configuration sources:
- Asset and software licenses:
- Test cases, reports, known issues, and release candidate:
- Store, backend, analytics, signing, and service-account ownership:
- Credentials transferred outside the repository:
- Access removed or retained after delivery:
- Final acceptance owner and date:

## 10. Quote request summary

- Decisions already fixed:
- Decisions requiring paid discovery:
- Smallest playable proof requested:
- Evidence required before scaling:
- Target service page or contact path:

Full explanation: <https://uploadforsoftware.com/insights/game-development-brief/>