orchestration

the conductor of agents

delegate only when the user or applicable project instructions authorize agents and the work has a useful independent boundary. keep one integration owner in the shared checkout; assign disjoint write paths and verify every agent report against live files.

disjoint write scopesbriefs by fileverifies every return

Agent delegation and multi-agent orchestration: executing plans through subagents, dispatching parallel agents on independent tasks, CLI delegation, and multi-session team coordination.

methodology

  1. choose the execution shape the request calls for: independent probes, sequential plan tasks with review, an explicitly requested CLI profile, or coordinated sessions. do not start a team merely because tools exist.
  2. brief each agent with outcome, evidence, exact read/write scope, dependencies, completion check, and constraints. choose an explicit available model and reasoning effort for the task.
  3. serialize overlapping mutations, reconcile returned evidence with fresh source, and run final verification as integration owner. never make a worktree, branch, merge, or push without the authority required by the global router.

contents

procedures

procedures the guru runs, one page each. read it, then follow it.

search pages

go to any page