<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Alexander Shustanov</title>
    <description>The latest articles on DEV Community by Alexander Shustanov (@alexandershustanov).</description>
    <link>https://dev.to/alexandershustanov</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F753553%2F873d0e1e-478c-4a34-97a4-404402ccc1f6.png</url>
      <title>DEV Community: Alexander Shustanov</title>
      <link>https://dev.to/alexandershustanov</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/alexandershustanov"/>
    <language>en</language>
    <item>
      <title>I stopped chatting with agents, instead ...</title>
      <dc:creator>Alexander Shustanov</dc:creator>
      <pubDate>Tue, 28 Jul 2026 14:45:56 +0000</pubDate>
      <link>https://dev.to/alexandershustanov/i-stopped-chatting-with-agents-instead--kk2</link>
      <guid>https://dev.to/alexandershustanov/i-stopped-chatting-with-agents-instead--kk2</guid>
      <description>&lt;p&gt;As for me, chatting with agent is really annoying. I write prompt, the agent replies, I correct it, it generates code, I need to skim througt it, correct againg, again and again. There are two big problems: context polution in agent history and simply unconvenient chatting UX.&lt;/p&gt;

&lt;p&gt;Instead of this I tried to build workflow where I do not need to chat. Actually, we already have a methodology that allows not to polute context – it called Spec Driven Development. I started to use the basic specs on the very begining of my journey with agents. But I used them in a very simple way. Firstly, I prepare a specification with an agent, and then I give it to another agent. But I still need to use a chat. Is is mostly annoying in a code review process. I need to reference some parts of code (many of them) and input my corrections into a chat window.&lt;/p&gt;

&lt;p&gt;That's why I started to build SpecBuddy. It is a plugin for IntelliJ-based IDEs that supports simple Spec Driven Workflow – around spec itself, not around a chat. I can write documents, review them, review code, send it back to agent, and everything of it – without even a line in a chat window.&lt;/p&gt;

&lt;p&gt;For now it works with Claude Code, Codex and OpenCode and support my own simplified spec-driven workflow, but soon OpenSpec will be supported.&lt;/p&gt;

&lt;p&gt;If you are interesting in, please, take a look. -&amp;gt; &lt;a href="https://specbuddy.dev" rel="noopener noreferrer"&gt;https://specbuddy.dev&lt;/a&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>productivity</category>
      <category>tooling</category>
      <category>programming</category>
    </item>
  </channel>
</rss>
