My twin built a full product this week.
A living directory of my principles.
- A blur that lifts when you subscribe.
- A card for each principle you can share.
- A back-end to write and publish new ones.
- An email system that notifies subscribers when anything changes.
- A year-long calendar showing every time I’ve added, changed or removed a principle.
- And a lot more…
Halfway through, I found a problem. When the page loaded, it jumped straight to an email input box. No context. No value. Just: give us your email.
I told my twin: demonstrate value first. Let the experience build before you make the ask.
It didn’t just fix the issue. It updated itself. It inferred the principle behind what I was saying and added it to its own taste file:
“Earned Friction: any gate must be earned through a value slope first. Jumping straight to the ask before delivering the experience is a trust violation. The user must feel the pull before we make the ask.”
I said fix it. It understood why. Then it kept building with that understanding.
When I announced Twin-Driven Development the most common question was how does this work?
Here’s the plain answer.
Before Twin-Driven Development…
You give an agent instructions. It executes them. Then it stops.
Now you’re back. Deciding what comes next. Writing the next batch. You are not writing code but you are always on call. That is the gap no one has solved. Not execution. The “what next.”
Agents can execute. They can work through any task list. They cannot refill it — until now.
Your taste, in a file
You answer five questions. We distill your answers into your twin.
The loop
From there, three things happen.
Before twin, you prompt the AI. With twin, your twin prompts the AI.
The AI asks your twin what to build next. Your twin answers.
The AI builds. It marks it done. Then it comes back to your twin: what’s next? Your twin answers. Then it builds again.
That’s it. Your taste in. Working products out.
You can drop in at any point. Say something. Your twin adds it to the roadmap and updates itself with what it just learned about you.
The compounding part
Some people are prompting their agents. You are training your twin.
Each interaction teaches it more. Your twin running tonight knows more about you than it did yesterday.
Your agent’s task list runs out. Your twin keeps building.
🔄
What could your twin build tonight while you sleep?
