- Content and mechanics evolve separately
- Asset lists omit import and performance requirements
- A prototype is mistaken for a production-ready game
games workflow hub
Multi-model workflows for games
Coordinate narrative, systems, environments, assets, QA, performance, and deployment around one playable slice.

- 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
One flow, bounded owners.
| Stage | Purpose | Suggested ownership |
|---|---|---|
| Player promise | Lock the target experience and slice | Planner + context keeper |
| Narrative and systems | Define story and mechanics interfaces | Writer + Coder |
| World and content | Specify space, encounters, assets, VFX, and audio | Planner + formatter |
| Production | Define budgets, pipeline, build, and data | Coder + tester |
| Playable acceptance | Verify feel, correctness, performance, and accessibility | Verifier + Reviewer |
Authored recipes
Start from a tested structure.
collaboration · Builder 10
Inspect + download →Game vertical-slice plan
Translate a game concept into one dependency-ordered vertical-slice production plan.
Roles + task guides
Understand each responsibility.
primary role
Open role →Planner
Turns an objective into an ordered, dependency-aware execution plan.
primary role
Open role →Coder
Implements or diagnoses software under the product’s real architecture and constraints.
support role
Open role →Tester
Turns requirements and implementation claims into reproducible checks.
support role
Open role →Context keeper
Protects the shared objective, canon, decisions, and accepted handoffs across a long workflow.
task guide
Follow guide →Choose Solo, Collaboration, or Dual
Match the orchestration topology to the dependency structure of the work.
task guide
Follow guide →Configure Majesty Obmil supervisor rules
Give the supervisor explicit review, stop, takeover, and team rules.