team-level

Cross-team workflow design is coordinated by orchestrating subagents to handle task decomposition, domain routing, and approval gates. This ensures alignment and governance across level design teams and product workflow areas through explicit user confirmation at each phase.

Managing hand-offs and dependencies during area design is handled by routing decisions to subagents and surfacing risks in the final report. The workflow requires explicit user confirmation before proceeding between steps, ensuring all cross-team dependencies are addressed.

Yes, you can use it to orchestrate both game level design and product onboarding workflows. It supports domain routing for game-concept areas, admin dashboards, API groups, CLI command groups, and data pipelines, gathering context to drive the appropriate workflow.

To start orchestrating a level design team, invoke the skill with /team-level followed by the level name or area to design. This initiates the orchestration process, capturing context and decomposing tasks for the chosen domain.

You should not use automated subagent orchestration when full autonomy is required without user oversight. The workflow mandates explicit user confirmation at each phase and only writes to memory after approval, making it unsuitable for fully automated or unsupervised pipelines.