team-executor

Load and execute predefined team-coordinate sessions via team-worker agents.

511|63|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/catlog22/Maestro-Flow --skill team-executor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-executor
Source: https://github.com/catlog22/Maestro-Flow/tree/main/.claude/skills/team-executor
Command: npx skills add https://github.com/catlog22/Maestro-Flow --skill team-executor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Lightweight session orchestration by loading and executing pre-defined team-coordinate sessions via team-worker agents. It ensures pure execution without analysis or role generation, requiring a session path.

Core Features & Use Cases

  • Lightweight session orchestration that loads and executes predefined team-coordinate sessions via team-worker agents.
  • No analysis or role generation; it executes existing tasks and reports results.
  • Robust state reconciliation and error handling during execution.

Quick Start

Start by invoking the skill with a valid --session path to load and execute a pre-existing team-coordinate session.

Frequently Asked Questions about team-executor

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

FAQPage Schema
How do I execute a predefined multi-agent workflow session?

Lightweight session orchestration executes predefined multi-agent sessions by loading team-worker agents via a valid session path. It dispatches workers, reconciles state with the TaskList, and reports results without generating roles.

What is the best way to run predefined team-worker sessions without analysis overhead?

Use a lightweight session executor that loads a valid session path to dispatch team-worker agents. It skips role generation and analysis, focusing purely on executing existing tasks while handling errors and reporting results.

Do I need a specific session path to start multi-agent orchestration?

Yes, a valid --session path is required to start multi-agent orchestration. The executor needs this path to load pre-existing team-coordinate session data, validate its structure, and spawn the appropriate team-worker agents.

How does the executor handle state reconciliation and errors during team-worker dispatch?

The executor reconciles state by syncing with the TaskList before dispatching team-workers. It manages errors during session execution, reporting failures to ensure reliable multi-agent workflow results.

When should I not use a lightweight session executor for multi-agent workflows?

Avoid using a lightweight session executor when your multi-agent workflow requires dynamic role generation or real-time analysis. It is designed strictly for executing predefined team-coordinate sessions and reporting results.