{"id":1470,"date":"2025-12-02T11:16:04","date_gmt":"2025-12-02T11:16:04","guid":{"rendered":"https:\/\/fredborg.org\/?p=1470"},"modified":"2026-01-07T10:30:09","modified_gmt":"2026-01-07T10:30:09","slug":"episode-2-the-setup-the-spec-mastering-agentic-coding-with-roo-code","status":"publish","type":"post","link":"https:\/\/fredborg.org\/?p=1470","title":{"rendered":"Episode 2: The Setup & The Spec \u2013 Mastering “Agentic” Coding with Roo Code"},"content":{"rendered":"\n

In my previous post, I explained why<\/em> I dropped GitHub Copilot for a custom AI workflow using Roo Code<\/strong> and OpenRouter<\/strong>. I needed more control, better context, and no rate limits.<\/p>\n\n\n\n

Now, it\u2019s time to stop talking and start building.<\/p>\n\n\n\n

In this episode, we are going to set up the entire environment, configure our multi-agent team, and most importantly, learn the difference between “Vibe Coding” and actual Agentic Coding<\/strong>.<\/p>\n\n\n\n

Here is how I set up my “Dev Team in a Box” to build a complex Business Central integration.<\/p>\n\n\n\n

Step 1: The Engine Room (OpenRouter)<\/h3>\n\n\n\n

The first step is to get our “fuel.” I use OpenRouter<\/strong> because it allows me to access top-tier models (like Claude 4.5 Sonnet and Gemini 3 Pro) on a pay-as-you-go basis.<\/p>\n\n\n\n

    \n
  1. Create an account:<\/strong> Go to openrouter.ai<\/a> and sign up.<\/li>\n\n\n\n
  2. Add Credits:<\/strong> You only pay for what you use. I usually add about $20, which goes a long way.<\/li>\n\n\n\n
  3. Get Your Key:<\/strong> Generate an API key. You will need this to connect Roo Code to the brain of the operation.<\/li>\n<\/ol>\n\n\n\n

    Step 2: Configuring the “Agents”<\/h3>\n\n\n\n

    Once Roo Code is installed in VS Code, we need to assign roles. This is where the magic happens. We don’t just use one model for everything; we assign the best<\/em> model for each specific job.<\/p>\n\n\n\n