team

Coordinate multiple agents executing bead-based plans with a lead worker model.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/cmtkdot/arc --skill team-cmtkdot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team
Source: https://github.com/cmtkdot/arc/tree/main/skills/team
Command: npx skills add https://github.com/cmtkdot/arc --skill team-cmtkdot

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinated multi-agent execution with a lead agent and self-claiming workers helps manage large, dependency-rich workflows by coordinating tasks, avoiding conflicts, and enforcing order.

Core Features & Use Cases

  • Lead/worker coordination for complex bead graphs and mixed dependencies
  • Gate-based checkpoints and shared-file conflict resolution to keep work moving
  • TDD-ordering enforcement and resilient execution with a team ledger

Quick Start

Start team-mode execution by running the interactive command /arc-start in your target repository.

Frequently Asked Questions about team

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

FAQPage Schema
How do I coordinate multiple agents to execute complex interdependent project plans?

Multi-agent orchestration coordinates a lead agent with self-claiming workers to execute complex plans, managing task dependencies and avoiding shared-file conflicts. It uses a lead-worker model with gate-driven checkpoints to enforce strict orderings.

What is the lead-worker model for multi-agent workflow management?

The lead-worker model assigns a lead agent to coordinate self-claiming workers across large dependency-rich workflows. It enforces TDD-ordering and uses a team ledger at .arc/team-ledger.json to track progress and ensure resilient execution.

How do I start team-mode execution for bead-based plans in my repository?

Start team-mode execution by running the interactive command /arc-start in your target repository. This initiates the coordinated multi-agent workflow using bead governance primitives like locking, pinning, and gates.

Do I need a specific environment flag to enable multi-agent team execution?

Yes, multi-agent team execution requires the team environment flag CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1 to be set. This enables the coordinated lead-worker functionality and bead governance primitives.

When should I use multi-agent orchestration for workflow management?

Multi-agent orchestration is best suited for large, interdependent projects where shared-file conflicts and strict orderings must be managed. It excels at complex bead graphs and mixed dependencies requiring gate-based checkpoints.

Can multi-agent orchestration resolve shared-file conflicts during plan execution?

Yes, multi-agent orchestration provides gate-based checkpoints and shared-file conflict resolution to keep work moving. Bead governance primitives like locking and pinning enforce predictable execution across coordinated agents.