What problem does it solve? Complex game features like combat systems, narrative content, UI overhauls, performance passes, and launch preparation require multiple specialist agents working in a specific order with clear handoffs. Without coordination, work falls through the cracks, conflicts surface late, and deliverables lack a single owner. ## Core Features & Use Cases - Five Spawn Recipes: Predefined coordination patterns for combat systems, narrative features, UI overhauls, performance passes, and launch prep, each defining participating agents, handoff chains, execution order, and conflict escalation rules. - Named Pipelines: Multi-step skill chains (such as new project and design iteration pipelines) that pass JSON state files between skills to carry context across phases. - Handoff Artifacts & Escalation: Mandatory structured handoff documents between agents plus explicit conflict-resolution tables that name which role wins each type of dispute. - Use Case: When asked to build a combat system, the orchestrator sequences the game designer's mechanics spec, the technical director's architecture document, parallel UX feedback design and QA test matrix, then runs an integration checkpoint with all four agents. ## Quick Start Ask the orchestrator to coordinate a cross-domain feature, for example: plan and coordinate a combat system build across design, tech, UX, and QA agents.
