games · collaboration · Builder 10

Game vertical-slice plan

Translate a game concept into one dependency-ordered vertical-slice production plan.

Uncrowned Planar, Urkel, Greedy, and Ivy Obmils trace four authored routes through an engraved brass-and-crystal workflow vault
Authored routes preserve the handoff while providers and models remain yours.
ONE REQUIRED OUTCOME

A scoped slice specification with systems, content, art, audio, QA, performance, and acceptance gates.

COLLABORATIONGame vertical-slice planRead-only authored structure · providers and models remain user-selected
  1. 01
    Plannercontext-keeper · game engineer
  2. 02
    Writereditor · master stylist
  3. 03
    Codertester · game engineer
  4. 04
    Plannerformatter · game-map specialist
  5. 05
    Reviewerdevils-advocate · UX designer
  6. 06
    Researchernote-taker · data scientist
  7. 07
    Writerformatter · technical writer
  8. 08
    Coderfact-checker · DevOps engineer
  9. 09
    Verifiertester · QA tester
  10. 10
    Reviewercontext-keeper · game engineer

Downloads contain assignments only—never provider keys, model choices, outputs, uploads, pairing details, or training material.

USE THIS WHEN
  • A concept needs a playable slice before full production
  • Narrative, mechanics, assets, and QA must agree
  • Scope drift is a material risk
DO NOT USE IT WHEN
  • The goal is to generate a complete commercial game in one model pass
  • No target platform or player loop has been chosen
AUTHORED STAGES

Every box owns a bounded handoff.

01
Planner · context keeper · heavy

game engineer

Define player promise, target platform, slice boundary, non-goals, and measurable definition of playable.

02
Writer · editor · medium

master stylist

Define the slice’s narrative premise, player motivation, dialogue needs, and canon locks.

03
Coder · tester · heavy

game engineer

Specify input, state, combat or interaction loop, failure states, save boundaries, and engine-facing interfaces.

04
Planner · formatter · heavy

game-map specialist

Author the playable-space sequence, encounter rhythm, traversal, blocking, and required environmental assets.

05
Reviewer · devils advocate · heavy

UX designer

Review Team One for player clarity, accessibility, scope, and contradictory dependencies.

06
Researcher · note taker · medium

data scientist

Establish platform budgets, asset counts, performance targets, and reference constraints.

07
Writer · formatter · medium

technical writer

Specify VFX, audio, UI feedback, tutorialization, and content-state requirements.

08
Coder · fact checker · heavy

DevOps engineer

Define build, content validation, telemetry, crash handling, and deployment checkpoints.

09
Verifier · tester · heavy

QA tester

Write functional, performance, accessibility, regression, and playtest acceptance cases.

10
Reviewer · context keeper · heavy

game engineer

Merge both tracks into one ordered production plan with owners, prerequisites, gates, and final acceptance criteria.