Original Reddit post

I’m a software engineer with ~20 years of Rails experience. I’ve been a startup CEO/CTO/founder for all of my career, so I’m not new to architecture or shipping production code. (Tens of thousands of commits.) I’m also strict about testing, especially for my LLM code. Right now I’m solo-founding an ambitious MVP — no team, no outside eng help until I can pay people from real revenue. To move faster, I’ve shifted into more of an orchestrator role with LLM coders: I plan thoroughly, then delegate implementation to Claude or Codex while I focus on architecture and review. The problem is this workflow has become a liability instead of a speedup. Here’s my current process:

  1. Planning: I run a structured planning loop that requires the final implementation plan to pass DHH’s Rails Core PR standards before any code gets written. 2. Local review: After the LLM implements, I run both a Codex review loop and a DHH-style code quality review loop until both come back clean. Nothing gets committed until it passes. 3. Cloud PR review: Once pushed, I run three independent PR review agents (Claude, Codex, and Cursor Bot) against each commit. Despite all of that, the cloud reviewers always surface major bugs and architectural issues that the local review missed. So I’m stuck copying findings back to the local agent, fixing, pushing, re-reviewing — rinse and repeat dozens of times on the same PR. A single PR routinely takes 30+ rounds of reviews and commits and hours or days before all three reviewers come back clean. I had some understanding for this a year ago, and the models weren’t quite so advanced . But it feels like something is wrong. At this point it’s not clear this is saving me any time versus just writing the code myself. I’ve tweaked instructs, added Skills, tried all sorts of stuff. Nothing leads to bug-free PR’s. What I’m wondering about from you: How have you structured your AI-assisted workflow to get code that’s right in the first couple of commits? I’m fine with a few rounds of review corrections (that’s normal). But 30+ commits per feature branch feels broken. What’s actually working for you? submitted by /u/NewMonarch

Originally posted by u/NewMonarch on r/ClaudeCode