Research Plan Implement — The Anti-Vibe-Coding Workflow

The Article That Never Should Have Existed A few weeks ago, I assigned a GitHub Copilot coding agent to write and publish an article for this site. I gave it a topic, pointed it at the codebase, and let it run. The agent did exactly what I asked: it wrote an article and opened a PR. The article was confident, well-structured, and completely hallucinated. It cited things that didn't happen, referenced features that didn't exist, and invented a narrative that had no grounding in reality. PR #105 stands as the monument to what happens when you skip the research phase. I caught it in review. But I shouldn't have had to. And that's the point. This is the vibe-coding problem — applied not just to code, but to anything an AI agent produces without first understanding its context. Agents that jump straight to output without grounding themselves in what's actually true produce confident-sounding garbage. The fix isn't a better model. It's a better workflow. Enter Dex Horthy and the RPI Framewor