team-level

Orchestrates cross-disciplinary teams to design complete game levels via gate-based workflow and Task prompts.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/LordKuper/agentic-game-studio --skill team-level-lordkuper
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-level
Source: https://github.com/LordKuper/agentic-game-studio/tree/main/.claude/skills/team-level
Command: npx skills add https://github.com/LordKuper/agentic-game-studio --skill team-level-lordkuper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates a cross-disciplinary level design team to design a complete game area—from concept to production-ready plan—through a structured, role-based workflow with integrated checks and approvals.

Core Features & Use Cases

  • Role-based team orchestration: coordinates narrative, design, art, systems, and QA roles to produce cohesive level concepts.
  • Gate-based decision workflow: advances steps via user-approved decisions and automated checks to ensure alignment.
  • Artifact generation and alignment: outputs a production-ready level design document at design/levels/[level-name].md with cross-team notes.
  • Context propagation to subagents: ensures every subagent receives full context (concept, pillars, and references) for consistent outcomes.

Quick Start

Orchestrate the multi-agent level design process by delegating roles, gathering context, and guiding stepwise collaboration until the level is defined.

Frequently Asked Questions about team-level

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

FAQPage Schema
How do I coordinate a multi-agent level design team for game development?

You can coordinate a multi-agent level design team by orchestrating cross-disciplinary subagents for narrative, layout, art direction, and systems through a gate-based workflow. This approach ensures cohesive level concepts and produces a production-ready level design document.

What does a production-ready level design document include for game areas?

A production-ready level design document includes narrative, layout, art direction, systems balance, accessibility, and QA coordination notes. It is generated at design/levels/[level-name].md with cross-team alignment details for the designated in-game area.

Can I use automated checks to balance game systems during level design?

Yes, automated checks are integrated into the gate-based workflow to validate systems balance and accessibility. These checks run alongside user-approved decisions to ensure the level design meets cross-disciplinary requirements before advancing to production.

How do I ensure subagents maintain context across narrative and art roles?

Subagents maintain context through full context propagation, ensuring every agent receives the complete level concept, design pillars, and references. This guarantees consistent narrative, art direction, and systems outcomes across the cross-disciplinary team.

When should I not use a cross-disciplinary team approach for level design?

A cross-disciplinary team approach is not suitable for simple level modifications or single-discipline tasks. It is designed for complete game areas requiring coordinated narrative, layout, art, systems balance, accessibility, and QA from concept to production-ready plan.