team-level

Coordinate a full design team into a gated workflow for level documentation.

72|7|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/striderZA/OpenCodeGameStudios --skill team-level-striderza
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-level
Source: https://github.com/striderZA/OpenCodeGameStudios/tree/main/.opencode/skills/team-level
Command: npx skills add https://github.com/striderZA/OpenCodeGameStudios --skill team-level-striderza

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates fragmented, ad-hoc level planning by coordinating a full level-design team to produce a complete, coherent area plan from narrative, world-building, and art direction through systems, accessibility, and QA.

Core Features & Use Cases

  • Team orchestration for level creation: Coordinates narrative-director, world-builder, level-designer, systems-designer, art-director, accessibility-specialist, and qa-tester in a gated workflow.
  • Decision gates with user approval: Uses interactive decision points to confirm outputs at step transitions before progressing.
  • Cross-document compilation: Produces a finalized level design document saved to design/levels/[level-name].md, including unresolved adjacent-area dependencies and accessibility concerns.
  • Validation and dependency handling: Detects missing adjacent area docs and prevents inventing content by requiring either placeholder references or running the prerequisite adjacent design skill.

Quick Start

Tell the AI to run /team-level with the level or area name you want created, such as “/team-level forest dungeon”.

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 level design roles into a single workflow?

Level design team orchestration coordinates narrative, world-building, art direction, layout, systems, accessibility, and QA roles into a single gated workflow with decision points for user approval at each step transition.

How do I generate complete level documentation from an area name?

Generate complete level documentation by providing an input level name or area descriptor, which triggers gated subagent task execution across all design roles to compile a finalized document saved to design/levels/[level-name].md.

What is the best way to handle missing adjacent area dependencies during world building?

World building dependency handling detects missing adjacent area docs and prevents inventing content by requiring either placeholder references or running the prerequisite adjacent design skill before proceeding.

Does this level design workflow include accessibility QA validation?

Yes, accessibility QA is integrated as a blocking step requiring explicit acknowledgment of accessibility concerns before final compilation of the level design document.

Can I use this for game documentation if I only need visual direction and layout?

This workflow orchestrates a full level-design team including art director and level-designer, but its gated execution requires narrative, world, systems, accessibility, and QA steps to complete before final compilation.

Why does the workflow stop at decision gates between design phases?

Decision gates use interactive decision points to confirm outputs at step transitions, ensuring user approval before the workflow progresses to the next specialized role in the level design pipeline.