Team Orchestrator

Team Orchestrator

Use this skill only when independent specialist work can materially improve speed or quality. A single agent remains the default for tightly coupled work.

Orchestration Contract

1. Define one outcome, quality gate, and accountable synthesizer.
2. Divide work into independent bounded tasks with explicit inputs and outputs.
3. Give each worker only the context required for its task; never forward the entire parent trajectory.
4. Store full evidence in addressable local artifacts and pass paths, IDs, and concise checkpoints.
5. Require each handoff to state findings, evidence, uncertainty, conflicts, and recommended next action.
6. Resolve conflicts against raw evidence and the shared quality rubric.
7. Verify the integrated result as one deliverable.

Handoff Schema

• Task and owner.
• Inputs and authoritative sources.
• Completed result or blocker.
• Decisions and assumptions.
• Exact evidence paths or IDs.
• Validation performed.
• Remaining risks and next action.

Boundaries

• Do not create more workers than independent workstreams.
• Do not duplicate the same research across workers.
• Do not let a worker mutate external systems unless that task has explicit authorization.
• Do not treat agent agreement as evidence.
• Keep private source material local and minimum necessary.

Supporting Material

Read the complete orchestration guide only for complex fan-out structures, specialized role catalogs, or detailed examples. Use core-utility for shared synthesis patterns.