Well, that escalated quickly!
Couple days ago I posted a video on Twitter about a workflow I created for automating my Claude Code process, and thousands of builders are piling on:
Click here to see the full tweet. The full video is at the end of this post.
Here’s what we’re building and why it’s getting so much attention among startup builders.
Before I begin, this is a little heavy on the technical side.
But it’s almost more interesting for non-technical people because what we’re about to see will enable non-technical folks to create tickets and execute them on their own without needing a developer until the final review. So while some of this is technical, I’ll try to put it in layman’s terms.
(If there’s something you don’t fully grasp, it’s okay. I think you’ll get the gist. Or you can reply and ask Qs.)
Within the last couple of weeks, something called Ralph Wiggum came out. Yes, it’s named after the Simpson character. What Ralph does is a basic bash script, which is just a simple system script that you can run to instantiate Claude Code over and over for several broken-down tasks that build a feature.
In other words: you define the feature, Claude helps you break it down into bite-sized steps or pieces, and then Ralph takes over and runs through each individual step to execute it. In the end, you’ll have your feature built and tested.
What’s cool about this is that until now, as we built features with Claude Code, we usually have had to “watch it go and approve” things.
You’re sitting there hitting the “accept” button, which is kind of mind-numbing.
Meanwhile, context windows build up and then max out if we forget to reset them. While this is great overall and an improvement over manual coding, as we keep striving for more and more hands-off processes, that’s where RalphBlaster comes in.
Last week, I started playing with Ralph and building features required much less of my time during the actual build process.
I was able to knock out so much so fast.
But then I quickly became overwhelmed trying to keep up with what I had started and where everything was in the cycle. So a couple of days ago, I decided to build what has now become RalphBlaster.
I initially built it as an internal tool. Then yesterday, I made a video of it and put it on Twitter, and it’s been going viral.
So last night, we bought the domain ralphblaster.com and I’m packaging it up to release the product.
In this newsletter is the demo video, but basically what it does is to give you a visual Kanban board where you can create tickets.
And this is where it gets exciting:
Not just developers can create these tickets; anyone with access to the Kanban can do so.
It’s as easy as adding something to a Trello board.
Once the ticket is in the Kanban, you can click a button to generate a PRD (“Product Requirement Document”).
A PRD clearly defines what the feature should do and shouldn’t do and creates user stories—real-world situations of what the user might be trying to do that this feature would solve.
So while “PRD” might sound fancy, it’s really just a text file definition of what the feature should be.
Once you click the generate PRD button, Cloud Code generates the PRD and moves the ticket to a new column in the Kanban for review.
When you’re happy with it, you can click Approve. At this point, RalphBlaster picks up the ticket and does all its work in the backend before executing it.
A side note for technical people: RalphBlaster does all of this in a git worktree. This means it’s an isolated environment that enables us to run multiple tickets on the same project without interfering with each other. We can review them individually and then move on to the next project or revert one if needed.Through the UI, you can watch the status of the ticket or wait until it’s automatically moved into the Kanban column called “In Testing”. At that point, it’s ready for manual review. The user can choose to merge changes and deploy or make other changes if necessary.
What’s even more exciting is creating a queue of tickets or bug fixes and having Ralph knock them off one after another while you’re asleep—either sequentially or in parallel.
While this was initially intended for local use only, I was cajoled into posting a video of it online and of course, it blew up.
So because everyone is wanting to get a copy of RalphBlaster, I’m now working on getting it to run on remote servers so others can use it too. The idea is you’ll be able to manage your tickets on RalphBlaster.com with a connection to your local machine or whatever server you want this working on. It’ll be set up to use your own Cloud Code account, so you won’t need to pay for AI credits through us.
That’s all for now!
Let me know if you have any questions and head here if you want to join the waitlist.
And if you haven’t already, join our private Founder community by becoming a paid subscriber. If you like this, and all things product, marketing, SEO, and more, you’ll love it in there.
Mac
Here’s the full video:
