tl;dr What’s the best way to transition a large, Claude-generated code base into Matt Pocock’s ralph based workflow? I’ve been working on a rather large project for the last few months (complex web service with dedicated front and back end, large volumes of data flow) and I’ve tried using Claude to develop the entire thing. I’ve had reasonable success so far, but I’ve also made mistakes–my code base is becoming large and disparate, spread over many, many files, and even small slices are taking large amounts of context because of all the “background information” Claude has learnt along the way. These large contexts mean that Claude is creating the features I ask for, but usually in a way that means the project is drifting from the original intent. I watched Matt Pocock’s excellent video on his AI workflow–agreeing with Claude what you want, creating a requirements document, creating Kanban issues, then executing in parallel where possible. What’s the best way for me to transition to using this system without losing the work that I’ve already done? Key questions as I see them: Is it worth salvaging existing code, or starting fresh? (would lose a couple of months work) Is there a “middle ground” where I can start fresh, but get Claude to pull in useful code from the existing project? Should my original project idea (to run through /grill-me) include the detail above, that I have an existing codebase but it’s starting to drift? How do I avoid losing my existing “todo” list? Some of the items on there are useful, but others may not survive focusing on the original specification (ie bug fixes for not-needed components) At what point is it worth refactoring the project to become a smaller number of large modules with a thin access layer, vice the currently hundreds of smaller modules? Cheers! submitted by /u/loopymon
Originally posted by u/loopymon on r/ClaudeCode
You must log in or # to comment.