team-level

Level design orchestration coordinates narrative, worldbuilding, art direction, layout, systems integration, accessibility review, and QA planning into a single gated workflow. It processes a level name alongside existing GDD and art bible constraints to output a production-ready area plan.

Cross-level dependency detection scans the design/levels/ directory for missing adjacent-area documentation. Instead of inventing missing content, it identifies unresolved dependencies and offers explicit handling options before proceeding with the level design workflow.

Accessibility enforcement during level creation collects BLOCKING, RECOMMENDED, and NICE TO HAVE concerns. It prevents the workflow from proceeding to the next phase if any BLOCKING issues are acknowledged, ensuring accessibility risks are surfaced and resolved before compilation.

Subagent delegation in Claude Code automates area creation by routing tasks to specialized roles like narrative-director, world-builder, and systems-designer. The workflow uses tool-based delegation with interactive AskUserQuestion gates to secure user approval at each major step transition.

Existing GDD, narrative, world-building, and art bible sources are required as constraints. The workflow uses these documents to ensure the resulting level design is coherent and aligns with established game systems, art direction, and worldbuilding lore before compiling into design/levels/[level-name].md.

The workflow halts at decision checkpoints using interactive AskUserQuestion gates to require user approval before moving forward. It also blocks progression if accessibility BLOCKING issues are acknowledged or if cross-level dependency checks detect unresolved adjacent-area documentation.