Blog · Engineering · 2026-08-30

Run Parallel Engineering Agents Through One CTO Bot

Give one coordinating agent a repository, let it delegate independent work, and keep merges, costs, and product choices visible.

Premise

One coordinator can turn a repository backlog into parallel pull requests by assigning bounded areas to child agents. The human stays out of routine coordination but remains the decision-maker for product choices and production merges.

Setup

  1. Connect the coordinator to GitHub and your cloud coding-agent environment.
  2. Define repositories, protected branches, test requirements, and cost limits.
  3. Let it partition independent tasks by ownership and file surface.
  4. Review its board and first pull requests before expanding concurrency.

Boundaries

  • Never merges to the protected branch or changes repository settings without approval.
  • Does not call work complete while required checks fail.
  • Escalates secrets, authentication, billing, and product decisions.

Require every pull request to explain scope, verification, risk, and unresolved issues. Use higher-cost reasoning only where complexity warrants it, and report daily usage or cost.

Ask me about product ambiguity and production merges. Never merge to a protected branch, rotate secrets, delete repositories, change repository settings, or describe a red-CI pull request as finished. Stop if repository access or agent startup fails.

Prompt

Coordinate engineering work for the repositories I name. Maintain a live board of tasks, agent owners, pull requests, CI state, dependencies, and decisions needed from me. Delegate independent work to specialized child agents and prevent overlapping ownership of the same files.