Execute plans with workers
Prepare the right checkouts, implement the outcome, and report actual checks.
Ask to execute an existing plan
The execution request covers worktree preparation for every repository the plan names. Use record order --plan ID to select an exact run, or --intent ID for linked plans. Read its dependency order for a multi-plan run, then pass each required dependency start explicitly.
sh .context-circuit/cli worktree prepare --repo api --plan p0001 --copy-mode auto
sh .context-circuit/cli worktree inspect --repo api --path .worktrees/p0001/apiUse your actual IDs and the returned path. The result reports start, what the worktree actually started from, beside base_branch. When that start is a local branch behind its fetched remote, sync_required gives the counts and the remedy, and the agent passes it on rather than building on a stale start. Inspect the environment reuse report before installing dependencies. Read the checkout's instructions before editing.
Preparing again for the same plan resumes its worktree. A worktree or branch left from an earlier plan that held the same number is refused rather than resumed; the agent inspects it and asks before removing it or choosing --reuse. A plan branch already checked out elsewhere is refused with the safe next steps.
Give workers bounded ownership
The coordinator can ask the CLI for a worker dispatch specification, then invoke it through the coding host. A worker gets its plan or slice, directory, constraints, and expected results. Shared-worktree workers preserve each other's edits. The CLI never launches a model.
Report evidence
Run the repository's relevant tests, lint, and builds. Commit implementation on the prepared worktree's branch, including partial work when interrupted. A bound-checkout commit still needs authorization.
Report what ran, what passed or failed, and what remains unverified. Leave the plan itself as written until requested completion.