Roam Turns Your Talking into Doing

April 17, 2026

I’m more of an ideas guy. Coding is a tool to bring ideas to life, and I’ve always been good at it, but the exciting part has always been the ideas themselves. When I was working on my PhD and considering an academic career, the thing that genuinely appealed to me about becoming a professor was having students to handle the legwork while I focused on the high-level thinking. Turns out I didn’t need to become a professor; with the state of the latest AI tools, I think I’ve finally found my grad student.

At Roam we have a role we call !nventors, essentially product managers and engineers rolled into one. A big piece of that is coming up with ideas (or “!deas” as we cheekily spell it), but you also have to be able to see them through to implementation. Going from “we should build this” to actually building it is where momentum really matters, and I’ve been tuning a small workflow in Roam that’s been really nice for that.

I’ve configured my office in Roam so that it auto-records Magic Minutes by default. Whenever I have a conversation there, I get a transcript, a summary, and the ability to prompt the meeting afterward. So when a technical discussion wraps up and we’ve sketched out a feature or a change we want to make, I don’t have to scramble to write everything down or translate the conversation into a task. I just ask Magic Minutes to write me a prompt for Claude to implement what we discussed. This moves my job more towards simply discussing features and software design, letting AI take care of many of the simple implementation tasks.

The model has pretty consistently formatted those prompts in a markdown code block, so I added a little copy-to-clipboard button to code blocks (throughout Roam) to make grabbing it frictionless. One click, then paste it into the Claude CLI.

What makes this actually useful is that Magic Minutes has the full context of the conversation, so the prompts it generates are way more detailed than anything I’d write from scratch. I’d usually be too lazy to spell out all the nuance. Magic Minutes does it for me.

And if there are open decisions that still need to be resolved before the task is well-defined, I can work through those in the conversation with Magic Minutes first. It has the whole meeting context to pull from, so it’s not starting cold.

This is part of a bigger thing we’ve been thinking about at Roam: post-meeting workflows. Meetings generate a lot of follow-up, and most of it is either forgotten or handled inefficiently. We’ve been working on distilling the key workflows where AI can actually help automate the natural next steps. This is a simple one, but for engineers it’s a pretty direct path from technical discussion to implementation. Expect more here, both for tighter vibe coding integrations, and for some pretty different applications we’re working on.