team-level

Multi-role level design orchestration coordinates narrative, worldbuilding, layout, systems, accessibility, and QA subagents into a single gated workflow. It uses phased checkpoints to collect outputs and compile a final level design document with cross-level dependency reporting.

Generate a complete level design document by spawning subagents across phased steps for narrative, systems integration, and QA planning. The workflow detects missing adjacent area files during cross-doc compilation to prevent invented content and reports unresolved dependencies.

Review mode gating uses user approvals at each phase transition via selectable checkpoints to control the level design workflow. You can set `--review full`, `--review lean`, or `--review solo` to adjust the depth of validation and interaction during the orchestration.

Yes, you can use the `--review solo` mode to run a full level design studio workflow tailored for solo game development. This mode orchestrates narrative, worldbuilding, layout, and systems subagents while reducing the frequency of user approval gates.

Blocking accessibility concerns are enforced before proceeding to the next phase of level design generation. The workflow requires resolving these issues or explicitly logging them as known gaps in the final level design document to ensure accessibility-aware production.

You need to provide game concept and design pillar documents before orchestrating a level design team workflow. The system reads these relevant design docs to inform narrative, worldbuilding, and systems integration subagents during the phased generation process.