team-level

Delegate game level design tasks to subagents and compile a level document.

1|Updated May 3, 2026

Search Tags:#game development #quality assurance #narrative #accessibility #agent orchestration #worldbuilding #level design

Ready to run

npx skills add https://github.com/imclab/xrA1-swarm --skill team-level-imclab

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: team-level
Source: https://github.com/imclab/xrA1-swarm/tree/main/.claude/skills/team-level
Command: npx skills add https://github.com/imclab/xrA1-swarm --skill team-level-imclab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of producing complete, coherent game area/level designs by coordinating multiple specialized roles instead of relying on brittle, ad-hoc brainstorming.

Core Features & Use Cases

Studio-style delegation to narrative, worldbuilding, level layout, systems design, art direction, accessibility, and QA through sequenced subagent prompts.
Gated collaboration with user approval at each step transition using selectable proposals so progress is controlled and validated.
Spec-driven compilation that consolidates narrative beats, layout, encounters, production concepts, accessibility checks, and QA plans into a single level design document saved to the expected path.

Quick Start

Invoke the Skill with a level name such as: orchestrate a complete level-design studio workflow for the area named "tutorial".

Frequently Asked Questions about team-level

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I orchestrate end-to-end game level design across multiple disciplines?▼

You orchestrate end-to-end game level design by delegating narrative, worldbuilding, layout, systems, art, accessibility, and QA tasks to sequenced subagents. This studio-style delegation ensures coherent game areas without relying on ad-hoc brainstorming.

How does agent orchestration work for game area creation?▼

Agent orchestration for game area creation works through staged task delegation to subagents, gated by user approval via selectable proposals at each step transition. This ensures progress is controlled and validated before final compilation into a level design document.

What is the best way to consolidate narrative beats and level layout into a single design document?▼

The best way to consolidate narrative beats, layout, encounters, production concepts, accessibility checks, and QA plans is through spec-driven compilation. This consolidates all specialized subagent outputs into a single level design document saved to the expected path.

Do I need existing design artifacts to generate a new game region?▼

Yes, generating a new game region requires existing design artifacts located under design/gdd, design/levels, design/narrative, and design/art directories. The workflow uses these inputs alongside a level name to check unresolved adjacent-area dependencies before proceeding.

Can I incorporate accessibility and quality assurance checks into my level design workflow?▼

Yes, accessibility and quality assurance checks are incorporated directly into the level design workflow. Dedicated subagents handle accessibility checks and QA plans, ensuring these aspects are validated during the gated collaboration process before final compilation.