orchestrator-session

A multi-phase workflow uses an orchestrator session that spawns a fresh subagent for each phase, collecting phase reports to maintain history and control transitions. The orchestrator delegates work while managing the overall session state.

In subagent orchestration, a structured poke back is a required response after a phase completes. It includes a completed tasks summary, changed files snippet, validation results, commit and push confirmation, and next-phase readiness to trigger the orchestrator loop.

Automate phase transitions for long-running sessions by using templates and references within the orchestrator session to standardize phase reviews, update phase history, and generate artifacts as each subagent completes its work and pokes back.

Yes, multi-phase orchestration satisfies requirements for HTTPS push-based commit workflows by requiring commit and push confirmation during the structured poke back. This ensures code changes are validated and remotely stored before the next phase begins.

Use an orchestrator loop for workflow planning when a multi-phase workflow requires isolation, validation, and structured transitions between tasks. It prevents context overload by spinning up fresh subagents per phase rather than retaining everything in one session.