complete

Goal orchestration to a merge-ready endpoint is automated by running the offload architect loop, which dispatches a codex builder slice-by-slice and waits for each slice via a backgrounded bridge. This ensures all commits are pushed to the branch before reaching merge readiness.

The offload architect loop is an automated workflow mechanism that runs contextual plan reviews and dispatches code construction in slices. It streamlines software development by ensuring code is built and verified incrementally before reaching a merge-ready state.

Yes, automating merge readiness requires both the offload skill and codex (gpt-5.5) for execution. These dependencies are necessary to drive the architect loop and dispatch the builder slices to push commits to the branch.

To start automating goal delivery, run the `/complete <goal>` command to initiate the process. This triggers the offload architect loop to begin contextual plan reviews and dispatch the codex builder slice-by-slice.

No, goal orchestration stops at the edge of merge by default and hands control to a human. This design allows for explicit authorization of merges, ensuring human oversight before any code is merged into the branch.

You should avoid using an automated architect loop if your software development workflow does not rely on codex or the offload skill, as these are strict dependencies. It is also unsuitable if your process requires immediate merging without human oversight.