team-level

Name: team-level
Availability: InStock
Author: Negentropy-Laby

Orchestrate subagents and approval gates for area and workflow design.

3|Updated Jun 3, 2026

Search Tags:#workflow #design #collaboration #orchestration #governance #team #level-design

Ready to run

npx skills add https://github.com/Negentropy-Laby/Constitution-Driven-Development --skill team-level-negentropy-laby

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: team-level
Source: https://github.com/Negentropy-Laby/Constitution-Driven-Development/tree/main/.agents/skills/team-level
Command: npx skills add https://github.com/Negentropy-Laby/Constitution-Driven-Development --skill team-level-negentropy-laby

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates area/workflow creation for game level design and product workflows, aligning cross-domain teams and ensuring governance, routing, and hand-off consistency.

Core Features & Use Cases

Task delegation and subagent orchestration to coordinate level design teams and product workflow areas.
Domain routing and context gathering to drive appropriate workflows (game-concept, level design, onboarding, admin dashboards, API groups, CLI command groups, data pipelines).
Gate-based decision flow with explicit user approvals at each phase and clear surface of dependencies and risks.

Quick Start

Invoke the skill with /team-level [level name or area to design] to start orchestration for the chosen domain.

Frequently Asked Questions about team-level

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

FAQPage Schema

How do I coordinate cross-team workflow design for game levels and product areas?▼

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.

What is the best way to manage hand-offs and dependencies during area design?▼

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.

Can I use this skill to orchestrate both game level design and product onboarding workflows?▼

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.

How do I start orchestrating a level design team with AI-guided governance?▼

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.

When should I not use automated subagent orchestration for workflow creation?▼

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.