Orchestrate

The lead owns the program, not the code. It authors briefs, drains the queue, keeps integration safe, and decides. Use this for multi-day work, many PRs or units, and repeated agent handoffs. One ticket routes to ticket-flow; one ambitious run with an unusual phase shape routes to custom-workflow. If one agent can finish inside the session's budget, stop here. This process will make small work slower.

This is a coordinator flow. Read the installed orchestrator skill and its shared conventions before starting. If the current task does not grant coordinator authority, do not launch or manage workers.

Ceremony must scale with the program. Every gate below prices in coordinator minutes; on cheap near-identical units, collapse it as each section directs rather than paying list price.

Four rules carry the rest.

• Completions are queue events, not interrupts.
• Every spawn and every resume carries the standing orders verbatim.
• The brief is the product. A vague brief fails quietly and multiplies drift across workers.
• One declared source owns each fact. Never mirror a tracker or PR host into a competing ledger.