4 ms·
I implemented some of his setup and have been loving it so far. My current workflow is typically 3-5 Claude Codes in parallel - Shallow clone, plan mode back
by ej88 9mo ago
I implemented some of his setup and have been loving it so far.
My current workflow is typically 3-5 Claude Codes in parallel
- Shallow clone, plan mode back and forth until I get the spec down, hand off to subagent to write a plan.md
- Ralph Wiggum Claude using plan.md and skills until PR passes tests, CI/CD, auto-responds to greptile reviews, prepares the PR for me to review
- Back and forth with Claude for any incremental changes or fixes
- Playwright MCP for Claude to view the browser for frontend
I still always comb through the PRs and double check everything including local testing, which is definitely the bottleneck in my dev cycles, but I'll typically have 2-4 PRs lined up ready for me at any moment.
- dbbk 9mo agoDo you prefer Playwright or the Chrome MCP?
- firemelt 9mo ago3-5 parallel claude code, do they work at same repo? do they work on same features/goals?
- ej88 9mo agoWe have a giant monorepo, hence the shallow clones. Each Claude works on its own feature / bug / ticket though, sometimes in the same part of the codebase but usually in different parts (my ralph loop has them resolve any merge conflicts automatically). I also have one Claude running just for spelunking through K8s, doing research, or asking questions about the codebase I'm unfamiliar with.