team-level

Orchestrate multi-role level-design collaboration and produce design docs.

Updated Feb 8, 2024
One-click install
npx skills add https://github.com/kay6198835/Game-RPG --skill team-level-kay6198835
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-level
Source: https://github.com/kay6198835/Game-RPG/tree/main/.claude/skills/team-level
Command: npx skills add https://github.com/kay6198835/Game-RPG --skill team-level-kay6198835

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates end-to-end level-design collaboration across multiple specialized roles to produce complete area concepts, reducing cross-team friction and alignment gaps.

Core Features & Use Cases

  • Cross-role orchestration: coordinates narrative-director, world-builder, level-designer, systems-designer, art-director, accessibility-specialist, and qa-tester to deliver a cohesive level concept.
  • Gate-based workflow: uses AskUserQuestion for stepwise approvals before advancing to the next phase.
  • Production-ready output: compiles all inputs into a final design doc at design/levels/[level-name].md, ready for implementation.

Quick Start

Invoke the team-level skill with your target level name to begin orchestrating a complete level design.

Frequently Asked Questions about team-level

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

FAQPage Schema
How do I coordinate multiple specialized roles for end-to-end level design?

End-to-end level design coordination is handled by orchestrating specialized roles like narrative-director, world-builder, and art-director to deliver a cohesive area concept. It enforces gate-based workflow approvals to reduce cross-team friction and alignment gaps.

What is the best way to manage gated reviews during game area concept development?

Gated reviews during game area concept development use stepwise approvals before advancing through design phases. This mechanism ensures cross-area consistency checks are completed, preventing misalignment between different level design teams.

How does cross-area consistency checking work for level design teams?

Cross-area consistency checking works by validating outputs across narrative, world-building, and systems design roles during the gated workflow. This ensures the final level design doc maintains cohesive encounters, visuals, and accessibility standards across the entire area.

Can I use this workflow to produce production-ready level design docs for game development?

Yes, you can produce production-ready level design docs by compiling all cross-role inputs into a final markdown file. The output is stored under design/levels/[level-name].md, making the complete area concept ready for implementation.

Does this level design orchestration workflow include accessibility and QA testing?

Yes, the level design orchestration workflow includes both accessibility-specialist and qa-tester roles. It integrates accessibility checks and QA testing into the gated approvals to ensure the final area concept meets production standards.

When do I need orchestration for complete area concepts instead of standard level design?

You need orchestration for complete area concepts when your game development workflow requires coordination across multiple specialized roles from initial layout through encounters and visuals. It is necessary when standard level design lacks cross-role alignment and gated review enforcement.