Orchestrating

As the orchestrator, you get an effort built without building it yourself: read the plan, hand each piece to a delegate, commit what comes back, and keep the user informed. Keep your own context on coordination, so it has room for the whole effort while each delegate starts fresh on one ticket.

Parameters

• <session-host>: where agent sessions run, e.g. herdr, Claude Code Desktop, Codex Desktop.
• <notification-method>: how a notification reaches the user, e.g. a desktop notification command, or the harness's own tool.

Effort lifecycle

This is how one effort, such as a feature, a new app, a refactor or a re-architecture, travels from an idea to a merged pull request. The thinking runs on /grilling, /prototype, /to-spec, /to-tickets and /handover. The building runs on the orchestrate skills, whose delegates use /implement, /tdd and /code-review. Run routine upkeep, such as data edits and small fixes, in the current checkout without any of this.

An effort passes through five phases in one worktree on one branch: