Project and intended user
Record the relevant facts, owner or open question.
A brief that names the decision, scope and people needed to start a useful game-development discussion.
Copy the template into your working document. Add what is known, mark unknowns and identify who can resolve them. No email is required.
Record the relevant facts, owner or open question.
Record the relevant facts, owner or open question.
Record the relevant facts, owner or open question.
Record the relevant facts, owner or open question.
Record the relevant facts, owner or open question.
Record the relevant facts, owner or open question.
Record the relevant facts, owner or open question.
Record the relevant facts, owner or open question.
Record the relevant facts, owner or open question.
Record the relevant facts, owner or open question.
Record the relevant facts, owner or open question.
Version 1.1 · Editable plain text (.txt) · No email required
Download the resource ↓SAMPLE — fictional planning example, not a Fluxoraa client project. Project: one menu flow in a prototype. Decision: can a first-time player start and replay with a controller? Target: one agreed PC configuration. Acceptance: start, pause, resume and restart work in a packaged build. Owner: the project reviewer (to be assigned). Excluded: full game production, online accounts and console submission.