team-level

Orchestrates six design subagents to produce complete game level design documents.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/onemanking/the-operator --skill team-level-onemanking
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-level
Source: https://github.com/onemanking/the-operator/tree/main/.github/skills/team-level
Command: npx skills add https://github.com/onemanking/the-operator --skill team-level-onemanking

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Designing a complete game level requires coordinating narrative, world-building, layout, systems, art, and QA perspectives, which is difficult to do consistently in a single pass. This Skill orchestrates a team of specialized subagents to produce a unified level design document. ## Core Features & Use Cases - Multi-Agent Orchestration: Sequentially spawns narrative-director, world-builder, level-designer, systems-designer, art-director, and qa-tester subagents, each contributing their domain expertise. - Interactive Decision Points: Presents each subagent's proposals as selectable options via AskUserQuestion, requiring user approval before advancing to the next design step. - Structured Output: Compiles all team outputs into a level design document saved to design/levels/[level-name].md with a summary of encounters, assets, and narrative beats. - Use Case: Invoke with an argument like "forest dungeon" to generate a full area design covering story purpose, spatial layout, enemy compositions, loot tables, visual direction, and a playtest checklist. ## Quick Start Invoke the team-level skill with the name of the level or area you want designed, such as "tutorial" or "final boss arena".

Frequently Asked Questions about team-level

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

FAQPage Schema
How do I design a complete game level with AI agents?

Invoke the team-level skill with the target area name as an argument. It spawns six specialized subagents in sequence covering narrative, world-building, layout, systems, art, and QA, then compiles their outputs into a level design document saved under design/levels/.

What subagents does the level design team include?

The team includes narrative-director, world-builder, level-designer, systems-designer, art-director, and qa-tester. Each handles a distinct domain such as story beats, spatial layout, enemy compositions, visual themes, or playtest checklists.

Can I approve or reject each design proposal during the workflow?

Yes. At each step transition the skill presents the subagent's proposals as selectable options using AskUserQuestion. You must approve the decision before the workflow advances to the next design step.

What input context does the level design workflow need?

The skill reads the game concept at design/gdd/game-concept.md, game pillars, existing level docs in design/levels/, narrative docs, and world-building docs for the area's region or faction before delegating tasks.

Where is the final level design document saved?

The compiled document combining all team outputs is saved to design/levels/[level-name].md. The skill also outputs a summary covering area overview, encounter count, asset list, narrative beats, and cross-team dependencies.