Launch the game development orchestrator for full pipeline coordination
Coordinates the full game development pipeline through orchestrated phase management and quality reviews.
/plugin marketplace add nethercore-systems/nethercore-ai-plugins/plugin install zx-orchestrator@nethercore-ai-plugins[action] - start, continue, status, or phase nameLaunch the game-orchestrator agent to coordinate the full Nethercore ZX game development pipeline.
Parse the argument to determine what action to take:
| Argument | Action |
|---|---|
| (none) | Check for existing project and ask user what to do |
start | Begin a new game project from scratch |
continue | Resume existing project from last checkpoint |
status | Show current project status and progress |
vision | Jump to Phase 0: Creative Foundation |
design | Jump to Phase 1: Design |
visual or assets | Jump to Phase 2: Visual Assets |
audio | Jump to Phase 3: Audio Assets |
implement or code | Jump to Phase 4: Implementation |
test or optimize | Jump to Phase 5: Testing & Optimization |
publish | Jump to Phase 6: Publish |
review | Run quality review checkpoints for current phase |
Check for existing project state:
.studio/project-status.mddocs/design/game-design.md (GDD)nether.toml (project manifest)Based on argument and state, invoke game-orchestrator agent:
Use Task tool with these parameters:
subagent_type: "zx-orchestrator:game-orchestrator"
description: "[Action]: [brief description]"
prompt: |
Action: [action from arguments]
Current State:
- GDD exists: [yes/no]
- Project manifest: [yes/no]
- Current phase: [phase name or "none"]
- Last checkpoint: [date/time or "none"]
[Include any relevant context from project-status.md]
Please [action-specific instruction].
For status action:
.studio/project-status.md if existsFor review action:
# Start fresh
/orchestrate start
# Continue where you left off
/orchestrate continue
# Check status
/orchestrate status
# Jump to specific phase
/orchestrate design
/orchestrate audio
/orchestrate publish
# Run quality review
/orchestrate review
When orchestrating, always show:
Remember: The orchestrator is HUMAN-DRIVEN. Always ask for user input on creative and design decisions. Never assume - always confirm with the user before major phase transitions.