games workflow hub

Multi-model workflows for games

Coordinate narrative, systems, environments, assets, QA, performance, and deployment around one playable slice.

Uncrowned Planar, gray Curious, purple Urkel, green Ivy, and orange Greedy Obmils occupy separate workstations while white Cleaner Obmil alone carries a faint halo
Six established Obmil identities share one expedition hall without becoming six competing projects.
PROBLEMS THIS ARCHITECTURE ADDRESSES
  • Content and mechanics evolve separately
  • Asset lists omit import and performance requirements
  • A prototype is mistaken for a production-ready game
OPERATING SAFEGUARDS
  • Treat asset creation, integration, validation, and licensing as separate completion gates
  • Bind every scene to real player input and state
  • Keep performance budgets platform-specific
  • Require rendered play tests, not only code checks
COHERENT STAGE SYSTEM

One flow, bounded owners.

StagePurposeSuggested ownership
Player promiseLock the target experience and slicePlanner + context keeper
Narrative and systemsDefine story and mechanics interfacesWriter + Coder
World and contentSpecify space, encounters, assets, VFX, and audioPlanner + formatter
ProductionDefine budgets, pipeline, build, and dataCoder + tester
Playable acceptanceVerify feel, correctness, performance, and accessibilityVerifier + Reviewer

Authored recipes

Start from a tested structure.

collaboration · Builder 10

Game vertical-slice plan

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

Inspect + download

Roles + task guides

Understand each responsibility.

primary role

Planner

Turns an objective into an ordered, dependency-aware execution plan.

Open role
primary role

Coder

Implements or diagnoses software under the product’s real architecture and constraints.

Open role
support role

Tester

Turns requirements and implementation claims into reproducible checks.

Open role
support role

Context keeper

Protects the shared objective, canon, decisions, and accepted handoffs across a long workflow.

Open role
task guide

Choose Solo, Collaboration, or Dual

Match the orchestration topology to the dependency structure of the work.

Follow guide
task guide

Configure Majesty Obmil supervisor rules

Give the supervisor explicit review, stop, takeover, and team rules.

Follow guide