orchestrator-session

Purpose

Manage a long-running session by delegating each phase to a new subagent, while the current chat acts as the orchestrator.

Orchestrator loop

1. Read the previous phase review and current phase plan.
2. Spawn a new subagent for the phase.
3. Require a "poke" back with:
   • Completed tasks summary
   • Files changed (tree snippet)
   • Validation results
   • Commit + push confirmation
   • Next-phase readiness
4. Update primary task list phase status and prepare the next phase plan.

Phase kickoff

• Each phase begins with a brief review of the previous phase review.