team-level

Cross-discipline level design is coordinated by orchestrating specialized subagents for narrative, world-building, layout, systems, art, and QA. This ensures structured task delegation and stepwise handoffs to unblock level development and align all domains.

Task delegation for level design is managed through built-in handoff and QA checkpoints. The workflow routes specific level-area requirements across narrative, systems, and art domains to ensure alignment before consolidating outputs into a final document.

Documenting a complete level design is best handled by consolidating cross-discipline outputs into a single markdown file. The final design artifacts are automatically saved to design/levels/[level-name].md to centralize the project deliverable.

Yes, this workflow applies to any level-area project requiring input from narrative, world-building, layout, systems, art, and QA teams. It scales to support any game development scenario needing structured cross-domain orchestration.

QA testing integrates into the level design workflow via built-in QA checkpoints. A dedicated qa-tester subagent validates the consolidated design artifacts during stepwise handoffs to ensure alignment before final document generation.