Coordinate multi-disciplinary level design into a final design document.
npx skills add https://github.com/dnkrow/skill --skill team-level-dnkrow
Please help me install this Agent Skill. Skill: team-level Source: https://github.com/dnkrow/skill/tree/main/claude-global/team-level Command: npx skills add https://github.com/dnkrow/skill --skill team-level-dnkrow
team-level coordinates a multi-disciplinary level-design workflow so a complete area/level can be planned end-to-end—from narrative and lore through layout, encounters, systems, production art concepts, accessibility review, and QA planning.
Use the team-level skill to design a specific area by invoking it with the area name as the argument.
High-intent search queries and answers about installing and using this skill.
You coordinate level design by running narrative, world-building, and art-direction sub-teams concurrently, then integrating outputs into layout, systems, accessibility checks, and QA. User approval gates at each stage ensure structured compilation into a final level design document.
Managing cross-level dependencies involves detecting missing adjacent-area documents and preventing content invention for undeveloped areas. The workflow flags unresolved dependencies during orchestration to ensure consistency across the full game world.
Accessibility reviews and QA planning are included by producing a severity-rated accessibility concerns list and a QA test plan covering the critical path and edge cases. These are integrated as final stages in the level design orchestration workflow.
Yes, a gated approval workflow supports parallel level design tasks by presenting sub-agent outputs at each major stage and requiring user approval before continuing. This coordinates narrative, world-building, and art direction concurrently while maintaining structured compilation.
You need a full level design orchestration workflow when planning a complete area end-to-end requires coordinating narrative, worldbuilding, art, systems, accessibility, and QA across a team. It enforces gated approvals and cross-level dependency detection that single-discipline approaches lack.
Orchestrating level design with parallel sub-teams requires strict context reads and cannot invent content for undeveloped adjacent areas. The workflow stalls if cross-level dependency detection flags missing prerequisite area documents that must be resolved before proceeding.
striderZACoordinate a full design team into a gated workflow for level documentation.
lgzarturoGenerate a Markdown test plan covering unit, integration, contract, edge cases, and regression.
wanghaishengOrchestrate a multi-agent team for complete game level design.
johnatas-henriqueCoordinate specialized subagents to produce complete game level design documents.
