Build a game around a clear, playable experience.

Game brief

A concise definition of the game objective, current state, audience, constraints, and decisions that shape this engagement.

• The game objective and owner are named.
• Known constraints and unresolved assumptions are recorded.

Build output

The concrete game work described by this service, prepared against the agreed scope and intended use.

• The agreed game scope is complete.
• The output has been checked against the primary game outcome.

Review record

A visible record of feedback, decisions, checks, and accepted limitations for the game.

• The agreed review checkpoint is complete.
• Open decisions are separated from accepted scope.

Handoff package

The approved files, documentation, access notes, and next actions needed to use or continue the game.

• Ownership and next actions are clear.
• Relevant files, links, and decisions are accessible.

01 / Confirm the build boundary

Confirm what the game must accomplish, what already exists, and which constraints cannot move.

02 / Create the working version

Build the game at the agreed level of depth while keeping dependencies and ownership visible.

03 / Verify the critical paths

Review the game against its intended audience, critical use cases, and agreed success signals.

04 / Prepare the release

Close the game cycle with accepted decisions, documented limits, and the next useful action.