Orchestrator: Multi-Agent Parallel Execution FAQs

Question 1

What is the Orchestrator skill used for?

Accepted Answer

It allows Claude Code to spawn multiple autonomous workers to perform different parts of a project plan in parallel, significantly reducing the time required for complex, multi-track tasks.

Question 2

How does Orchestrator prevent agents from overwriting each other's work?

Accepted Answer

The skill implements a file reservation protocol. Workers must claim specific file scopes before editing and are restricted from touching files assigned to other tracks until the reservation is released.

Question 3

Is TDD mandatory for parallel workers?

Accepted Answer

By default, all workers follow a Red-Green-Refactor cycle to ensure code reliability. However, this can be disabled using the --no-tdd flag if the specific task doesn't require automated testing.

Question 4

Does this skill require an external MCP server?

Accepted Answer

Orchestrator uses a lazy-load pattern. It prefers the Bun-based Agent Mail CLI for zero-token-cost coordination, falling back to MCP tools only if the CLI is unavailable.

Question 5

How do I trigger the parallel execution mode?

Accepted Answer

It triggers automatically when a plan contains multiple 'Track Assignments'. You can also trigger it manually using commands like /conductor-orchestrate or phrases like 'run parallel'.

Orchestrator: Multi-Agent Parallel Execution

Orchestrator: Multi-Agent Parallel Execution

주요 기능

사용 사례

주요 기능

사용 사례