Yeah. Personally I haven't found a workflow that relies heavily on detailed design specs, red/green TDD followed by code review. And that's fine because that's how I did my work before AI anyway, both at the individual level and at the team level. So really, this is no different than reviewing someone else's PR, aside from the (greatly increased) turnaround time and volume.
I’ve found it helpful to have a model write a detailed architecture and implementation proposal, which I then review and iterate on.
From there it splits out each phase into three parts: implementation, code review, and iteration.
After each part, I do a code review and iteration.
If asked, the proposal is broken down into small, logical chunks so code review is pretty quick. It can only stray so far off track.
I treat it like a strong mid-level engineer who is learning to ship iteratively.
I play Claude and Codex against each other
Codex is pretty good at finding complex bugs in the code, but Claude is better at getting stuff working
That's pretty much how I use Codex.