team-orchestrator

Determines execution level and orchestrates agent teams for multi-agent workflows.

Updated Feb 20, 2026
One-click install
npx skills add https://github.com/jota-batuta/batuta-dots --skill team-orchestrator-jota-batuta
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-orchestrator
Source: https://github.com/jota-batuta/batuta-dots/tree/main/BatutaClaude/skills/team-orchestrator
Command: npx skills add https://github.com/jota-batuta/batuta-dots --skill team-orchestrator-jota-batuta

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Decides the optimal execution level for any task and orchestrate Agent Teams when complexity warrants it, preventing bottlenecks and miscoordination in multi-agent workflows.

Core Features & Use Cases

  • Determines LEVEL 1 solo, LEVEL 2 subagents, or LEVEL 3 team based on file count, scope, and inter-task communication needs.
  • Spawns Agent Teams with contracts, manages cross-teammate inputs/outputs, and ensures safe parallelization for complex features.
  • Use Case: when a multi-module feature requires coordinated work across pipeline, infra, and data domains, the orchestrator configures the appropriate team setup.

Quick Start

Provide a task description and let the Team Orchestrator determine the best execution strategy and spawn the appropriate agents.

Frequently Asked Questions about team-orchestrator

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

FAQPage Schema
How do I coordinate multi-agent workflows for cross-scope software changes?

Multi-agent workflows for cross-scope changes are coordinated by determining the optimal execution level and spawning agent teams with defined contracts to manage inter-task communication and prevent bottlenecks.

When should I use parallel execution with subagents instead of a solo agent?

Parallel execution with subagents is warranted when task complexity involves multi-file changes, cross-scope work across pipeline, infra, or data domains, and inter-task communication needs that exceed solo agent capabilities.

How does a contract-first protocol work for agent team orchestration?

A contract-first protocol for agent team orchestration works by defining file ownership and cross-teammate inputs/outputs upfront, ensuring safe parallelization and preventing miscoordination in complex multi-module features.

What is the best way to prevent bottlenecks in multi-agent software engineering tasks?

Bottlenecks in multi-agent tasks are prevented by implementing an execution gate that selects Level 1 solo, Level 2 subagents, or Level 3 team execution paths based on file count, scope, and communication needs.

Can I use team orchestration for multi-module features spanning pipeline and data domains?

Yes, team orchestration is designed for multi-module features spanning pipeline, infra, and data domains, dynamically forming agent teams with contracts to ensure coordinated collaboration across domains.