I tried out Ralph Loops (by Geoffrey Huntley). You give an agent a list of features and it picks a feature, builds it, picks the next. No input required. Until the list runs out.
Yesterday, I read about a developer who used to sleep 7 to 8 hours. Now he is up at 5am feeding his agents. Not because a boss told him to. Because the agents are waiting.
When the queue is done, the agent has no idea what to do next. It stops and waits for you.
I created Twin-Driven Development to fix this.
- Old TDD meant write the tests first.
- New TDD means build your twin first.
A .twin file is the .env for your taste.
Your .twin knows how you think:
- What do you do when two options look equal?
- What do you ship first and what can wait?
- How do you think about trade-offs?
- What does “done” look like to you?
- What do you refuse to build?
Your twin keeps building. You are no longer the bottleneck.
twin-cli ships with everything you need: init to build your twin, plan to build and extend your roadmap, build to let your twin execute it.
Pass –loop and it builds, plans what comes next and builds again.
For as long as you want.
Not human in the loop. Twin in the loop.
mkdir habit-app && cd habit-app
npx twin-cli init # how you think, in a file
npx twin-cli plan # your twin extends your roadmap
npx twin-cli build # your twin builds itRun plan and your twin extends your roadmap.
Run build and your twin builds those stories.
You can run plan and build manually in cycles, staying in control of each step.
Or pass --loop and your twin builds, plans what comes next, then builds again.
Start with a few user stories before you let it loop.
npx twin-cli build # your twin builds the current stories
npx twin-cli build --loop # your twin builds and keeps going
npx twin-cli build --loop --stories 5 # your twin stops after 5 stories
npx twin-cli build --loop --minutes 30 # your twin stops after 30 minsYou do not have to keep re-inserting yourself with Twin-Driven Development. Or waking up at 5am.
As I write this, my twin is building a living directory for me. Seven years ago I published 100 Rules to Live By. Now my twin is building an interactive app with the current version of my rules.
Dru.twin built a Git style log that tracks each principle like a code change, with a history of what was added, reworded and removed. Now it’s working on a principle randomizer that shows a different rule on each visit. I may have gotten there eventually. My twin didn’t wait.
And it keeps going. Each loop, the product improves.
Build your twin. Stop being the ceiling on your own product.
👥
What would your twin ship that you keep putting off?
