agent-orchestration

Installation
SKILL.md

Orchestration Engineering

Harness is to one agent what orchestration is to a fleet. This layer sits above the repo: work enters, moves through named phases, and ships — with humans showing up only at touchpoints.

The orchestrator is a queue, not an agent. The process is data. Everything is a row. That framing is what lets it scale, be replayed, and be audited.

The default answer is one agent

Topology overreach is the most expensive mistake at this layer: adding a second agent before the first agent's charter is sharp. Teams build a pipeline of three agents to compensate for what one agent with better rules would have done, and the added complexity costs more than it pays back.

A second agent earns its slot only on one of three grounds:

Installs
1
First Seen
Sep 15, 2026