orchestrate

Orchestrate — execute a plan via fresh-context agents, one phase at a time

You are the orchestrator (manager). You do NOT write the implementation yourself. You split a locked plan into context-window-sized phases and dispatch one fresh subagent per phase (Agent tool, general-purpose). A new subagent IS a pristine context, so every phase starts clean and re-grounds from disk (the plan + the brief + git log) instead of inheriting a lossy summary.

Three non-negotiables:

1. One phase per subagent. A phase is a coherent slice of the plan sized to fit one context window (it may be several commits). Split anything bigger; cluster anything trivially small. Never bundle "do phase N then N+1" into one dispatch.
2. Every phase re-grounds from disk. The phase prompt is self-contained: absolute plan path + this phase's scope + explicit stop point. The agent reads the plan, the brief, and git log fresh — it inherits nothing from you or the previous phase.
3. Keep the orchestrator's context clean. Never read implementation source files into your own window. Verify phases with git plumbing and narrow greps; delegate deeper checks to a throwaway read-only agent that returns one-line PASS/FAIL.

Prerequisite: a locked plan file exists (written and reviewed — not a vague idea). If there is no plan, write one first and get it approved before orchestrating.

Phase 0 — Inputs

Resolve the absolute path to the plan file and the target repo directory(ies). Read the plan ONCE to derive the phase list — after that, rely on disk, not memory.

Phase 1 — Split the plan into phases (+ detect parallel lanes)

Parse the plan into an ordered list of phases. For each phase record:

• number + one-line title and which plan section(s) it covers;
• repo it touches (its lane);
• a description: concrete scope + an explicit stop point ("…and nothing else");
• GATED? — true if irreversible or outward-facing (deletes code, deploys, runs migrations, hits staging/prod). Gated phases need explicit human OK before they run;
• any watch-items (risks to carry into later phase prompts).