What problem does it solve?
It coordinates multiple specialized sub-agents to produce a complete, consistent game level/area design document, aligned to narrative, world rules, visual direction, gameplay systems, production concepts, and QA needs.
Core Features & Use Cases
- Team orchestration for area creation: Delegates to narrative-director, world-builder, level-designer, systems-designer, art-director, accessibility-specialist, and qa-tester in a structured sequence.
- Cross-discipline consistency gates: Uses user approvals after each major step to prevent contradictions (especially between visual targets and layout, plus accessibility blocking issues).
- Cross-level dependency checking: Detects missing adjacent area docs and prompts the user to either create placeholders (UNRESOLVED) or run the needed prior skill.
- Accessible-by-design review: Surfaces navigation clarity and color/contrast/cognitive-load issues with severity (BLOCKING / RECOMMENDED / NICE TO HAVE).
- Outputs a ready-to-implement design doc: Compiles everything into a standardized level design document saved to design/levels/[level-name].md, then produces a detailed summary and open questions list.
Quick Start
Invoke team-level with the level or area name you want to design, and follow the approval prompts between steps.