team-dispatch

To automate epic work across multiple agents, you deploy a structured team plan from an arc issue graph. This maps teammate roles from labels, creates per-issue tasks, and spawns role-based agents to parallelize the workload.

Mapping arc labels to teammate roles occurs automatically when the skill gathers team context from an arc epic. It identifies required roles based on the applied labels and assigns per-issue tasks to the correct owner identities.

You cannot use this orchestration without an active arc project. Deploying role-based agents requires an active arc project, a running arc server, and labeled issues in the graph to map to team roles.

Parallel task execution handles dependencies by monitoring progress and validating closures. It automatically resolves unblocked work, ensuring downstream tasks begin only when their prerequisite per-issue tasks are completed.

The best way to coordinate multiple agents is translating the arc issue graph into a structured team plan. This enables parallel work across roles and ensures consistent task ownership instead of manual coordination.

Spawning teammates requires labeled issues because the skill uses those labels to map out required roles. Without labeled issues, the workflow cannot identify teammate roles or assign per-issue tasks to correct owners.