One-click install
npx skills add https://github.com/easonlao/jiazi-game --skill team-level-easonlao
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-level
Source: https://github.com/easonlao/jiazi-game/tree/main/.claude/skills/team-level
Command: npx skills add https://github.com/easonlao/jiazi-game --skill team-level-easonlao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It coordinates multiple specialized sub-agents to produce a complete, consistent game level/area design document, aligned to narrative, world rules, visual direction, gameplay systems, production concepts, and QA needs.

Core Features & Use Cases

  • Team orchestration for area creation: Delegates to narrative-director, world-builder, level-designer, systems-designer, art-director, accessibility-specialist, and qa-tester in a structured sequence.
  • Cross-discipline consistency gates: Uses user approvals after each major step to prevent contradictions (especially between visual targets and layout, plus accessibility blocking issues).
  • Cross-level dependency checking: Detects missing adjacent area docs and prompts the user to either create placeholders (UNRESOLVED) or run the needed prior skill.
  • Accessible-by-design review: Surfaces navigation clarity and color/contrast/cognitive-load issues with severity (BLOCKING / RECOMMENDED / NICE TO HAVE).
  • Outputs a ready-to-implement design doc: Compiles everything into a standardized level design document saved to design/levels/[level-name].md, then produces a detailed summary and open questions list.

Quick Start

Invoke team-level with the level or area name you want to design, and follow the approval prompts between steps.

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 disciplines for game level design documentation?

Game level design documentation is coordinated by delegating narrative, world, layout, systems, art, accessibility, and QA planning tasks to specialized subagents in a structured sequence with user approval gates to ensure cross-discipline consistency.

How to ensure narrative and world rules are consistent when creating a new level?

To ensure narrative and world rules are consistent when creating a level, the workflow applies explicit dependencies on GDD pillars and adjacent level documentation, pausing for user approvals after each major step to prevent contradictions.

Does this level production workflow handle accessibility review for color contrast and cognitive load?

Yes, the level production workflow includes an accessibility review that surfaces navigation clarity, color, contrast, and cognitive-load issues, classifying each with a severity level of BLOCKING, RECOMMENDED, or NICE TO HAVE.

What happens if adjacent area documentation is missing during level design?

If adjacent area documentation is missing during level design, cross-level dependency checking detects the gap and prompts you to either create placeholder documents marked UNRESOLVED or run the needed prior skill.

How do I compile a level design document with cross-level dependencies and open questions?

You compile a level design document by running the team orchestration workflow, which outputs a standardized markdown file saved to design/levels/[level-name].md alongside a detailed summary and a list of open questions.