Architect-builder cross-vendor loop
A two-vendor loop that pairs Claude as architect with Codex as builder, using the repo itself as shared memory: the architect writes specs, the builder implements one item per iteration, and the architect reviews the diffs on the next pass.
Implementation note
When to use: tasks where planning quality and implementation throughput are different problems — you want one model doing deliberate architecture and another grinding out code, with a review pass between them. How it works: Claude plays architect, Codex plays builder, and the repo itself is the shared memory. The architect writes plan and spec files into the repo; the builder implements one item per iteration from those specs; on the next pass the architect reviews the resulting diffs and updates the plan. Neither agent holds conversational state about the other — everything they know about each other's work lives in files and git history. Safety: the architect-reviews-diffs step is the built-in check — implementation drift gets caught on the next planning pass rather than accumulating silently. One item per builder iteration keeps changes bounded and attributable. Cap iterations on both sides and keep the spec files small enough that fresh-context reads stay reliable.
Source: DanMcInerney/architect-loop ↗graded C · 60/100 — how grades work →
More planning loops
Implement feature X autonomously
Ralph runs until it outputs DONE, implementing the feature end-to-end over up to 20 iterations.
Ship GOALS.md phases 1-13
Implement each GOALS.md phase with tests and validation, committing and pushing after stable milestones until unblocked.
Execute roadmap phases to completion
Work through each phase in your roadmap, verify each one, run the final audit, and stop when all phases pass.