completer

Automate Completer agent handoffs by orchestrating audits of the latest pass-file and spawning the next Oz agent Completer. This coordinates pass-file versioning and branch updates to maintain continuous roadmap momentum for Largo V2.

Pass-file versioning is the process of auditing the latest pass-file and creating a new one with detailed change summaries. It prevents workflow drift by maintaining explicit validation of pass-file states and clear audit trails during agent handoffs.

Prepare subsequent work by triggering the Completer orchestrator to audit the latest pass-file state. It validates current progress, generates an updated pass-file with change summaries, and spawns the next Oz agent Completer to continue the workflow.

Yes, you can coordinate multiple Completer runs without conflicts. The orchestrator applies robustness and safety through explicit validation of pass-file states and controlled agent handoffs, ensuring continuous progress while preventing drift.

Largo V2 workflows lose momentum without automated orchestration to manage pass-file versioning and branch updates. The Completer orchestrator solves this by automatically auditing pass-files and spawning the next Oz agent to maintain roadmap progress.

You should not use an automated orchestrator for agent handoffs if your workflow lacks established hooks for spawning Oz agents or if pass-file states cannot be explicitly validated, as the Completer relies on these to prevent drift.