How Orchestration Works
The orchestration engine is the core of the Team6 operating system. It's what turns a company goal into a coordinated sprint — with AI agents and human owners working together across your entire R&D organization.
This isn't a smarter copilot. It's the execution layer for AI-first R&D.
Full Sprint Example
Here's how a complete sprint looks — from goal to merged PRs:
Tasks execute in dependency order. Each task follows the orchestration cycle detailed below. The result: coordinated PRs, each owned and approved by a team member.
How It Works
1. Collaborative Planning
Your team describes the goal. The Product Manager agent drafts the plan through an interactive sprint planning wizard — but your team owns it:
The AI accelerates planning — but every decision is made by your team. No task runs without a human owner. No sprint starts without human approval.
2. Parallel Execution in Isolated Workspaces
Once approved, the engine executes tasks on your project's dedicated worker machine — your workloads never share compute with another organization.
Each task gets its own isolated workspace using git worktrees — an isolated working directory with a unique feature branch, but sharing the underlying git history. The first task on a repository triggers a full clone; every subsequent task creates a worktree from that base in under a second (10x faster than cloning). Tasks at the same dependency level run simultaneously. Tasks only start when their dependencies are complete.
- Multiple concurrent agents (configurable), each in a separate process
- Per-project BullMQ queues (
agents-{projectId}) for workload isolation - Auto-retry on failure with exponential backoff (5 attempts)
- Agent heartbeat monitoring every 30 seconds — stale agents are detected and recovered
- Autoscaling adjusts worker capacity based on queue depth
- Workspaces are automatically cleaned up after task completion
3. Agent Delegation
When an agent encounters work outside its specialty, it delegates subtasks to the right specialist:
The parent task resumes automatically when all subtasks deliver their PRs.
4. Multi-Repository Coordination
A single task can span multiple repositories:
The engine coordinates changes across repos (e.g., API contract in the backend + client integration in the frontend) and creates separate PRs in each repository, linked to the same task.
How a Single Task Flows Through the System
Here's exactly what happens when a task enters the orchestration engine — from assignment to merged PR.
This cycle runs in parallel for every task in the sprint.
What Makes This Different
| AI Coding Assistants | Team6 |
|---|---|
| One agent helps one developer | Multiple specialist agents integrated into the whole team |
| Developer writes the prompt, manages the output | Orchestration engine plans the sprint, manages dependencies |
| No concept of a sprint or task graph | Full sprint planning with dependency resolution |
| Runs on the developer's machine | Dedicated worker machine per project, fully isolated |
| One task at a time, sequentially | Parallel execution across isolated workspaces |
| Single repo, single context | Multi-repository coordination with linked PRs |
| Developer decides when it's done | Human owner reviews, iterates with the agent, and approves |