I have Claude code is set up well enough to where I feel confident that when it creates a spec and plan that the implementation will be correct assuming the plan is correct. I spend most of my time reviewing the plan. Then I will send off a 20 part sub agent driven plan, running 2 to 5 of these in parallel. I don’t read the code I just let it rip after plan is reviewed. Changing thousands of lines per day with mostly good results. The key is to have the guardrails in place to prevent it from conflicting changes or deviating from plan. I let this run for 4 or 5 hours at a time then check back later to see results. Sometimes I don’t even test it for a whole day and just let it rip. My code is play dough. When I say my code is play dough I mean that it is able to be molded and shaped and reshaped into whatever I need it to do. It is constantly changing and I don’t have to worry about that all I have to do is make sure the plans and specs look right. Anyone else successfully vibe coding at this level? Wanted to hear more from you all. I utilize Serena to replace grep in most of the calls with symbol lookups. I also run several custom MCP servers to assess code quality. I vibe coded code quality checkers to ensure that the agents don’t go out of line. I also use superpowers plugin to make and implement the plans. I review every spec I put out. We have a code base of 350,000 lines in a well structured monorepo. I can work on multiple projects at the same time. Some projects are connected or dependencies. The Claude code navigates it well. The system works fairly well tbh. submitted by /u/Counter-Business
Originally posted by u/Counter-Business on r/ClaudeCode