
Episode #11
Give Your Agents Superpowers: Jesse Vincent Live with Tim O’Reilly
As the former chief maintainer of Perl 5 and project manager for Perl 6, as well as a longtime programming team leader, Jesse Vincent learned early that getting good work from smart, capable people often depends less on giving orders than on providing context, clear goals, and useful feedback. That experience turned out to be unexpectedly useful for working with AI agents. Now, as the founder of applied research lab Prime Radiant, he’s created Superpowers, a framework that teaches Claude Code to work more like a disciplined senior engineer. Jesse joined Tim O’Reilly to explain what building Superpowers has taught him about agentic development and why the scarce human skills for software folks are now knowing what you want, expressing it clearly, and judging whether the result is any good. Jesse’s approach borrows as much from management as from software engineering. He and Tim discussed why agents respond better when you explain why a rule exists, why prohibitions often fail, and how the techniques Jesse learned managing junior programmers are helping him now. Jesse approaches agents less like tools that need perfect instructions and more like colleagues who need context, clear goals, and well-designed processes, so his agents have roles, journals, and even a "therapist" that helps them update their own operating instructions. But the goal of Superpowers isn’t to make agents imitate humans. It’s to give them enough structure and discretion to turn high-level direction into the intended result while still speaking up when something looks wrong. That puts more responsibility on humans, not less. Jesse makes his agents surface unknowns before they start, explain plans back in small pieces, and prove that their work actually functions. He also avoids letting the same agent that produces the work also certify it. As AI takes over more of the labor of production, Jesse argues, writing, curiosity, domain knowledge, taste, and judgment become more valuable. The programmer’s job is changing, but the need to understand what should be built, communicate that intent, and recognize good work when you see it isn’t going away.

