team-level

Cross-discipline level design is coordinated by delegating tasks to specialized subagents covering narrative, world-building, art, and QA. The Skill gathers context from existing design docs, applies decision gates for user approvals, and outputs a cohesive level plan stored as production documentation.

End-to-end level documentation is generated by routing lore, art direction, and mechanics through decision gates for user approval. The Skill orchestrates subagents across narrative, world-building, and art roles to produce a complete production doc with a summary of open questions.

Yes, subagents can manage world-building and QA-testing for a single game level. The Skill orchestrates specialized roles including world-builder, qa-tester, and systems-designer to collaboratively gather context, generate a level plan, and surface open questions for review.

This approach relies on gathering context from existing design docs to ensure cohesive level creation. Without prior design documentation, the subagents lack the foundational lore and systems context needed to generate a coordinated level plan and accurate production documentation.

Decision gates and reviews during level production are handled using AskUserQuestion to surface options and obtain user approvals before progression. This ensures the cross-disciplinary team of subagents receives explicit approval at each design phase before generating the final document.