<?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: Chandrakiran GR</title>
    <description>The latest articles on DEV Community by Chandrakiran GR (@chandrakiran_gr).</description>
    <link>https://dev.to/chandrakiran_gr</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%2F3987630%2F9e20384d-0f50-41de-9480-7b5eddef40c5.jpg</url>
      <title>DEV Community: Chandrakiran GR</title>
      <link>https://dev.to/chandrakiran_gr</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/chandrakiran_gr"/>
    <language>en</language>
    <item>
      <title>How Vokal’s Onboarding Assistant Turns Plain Language Into a Working Agent Workflow</title>
      <dc:creator>Chandrakiran GR</dc:creator>
      <pubDate>Mon, 22 Jun 2026 01:12:30 +0000</pubDate>
      <link>https://dev.to/chandrakiran_gr/how-vokals-onboarding-assistant-turns-plain-language-into-a-working-agent-workflow-137o</link>
      <guid>https://dev.to/chandrakiran_gr/how-vokals-onboarding-assistant-turns-plain-language-into-a-working-agent-workflow-137o</guid>
      <description>&lt;p&gt;Most AI agent demos begin after the setup is already finished.&lt;/p&gt;

&lt;p&gt;The agent exists. The role is written. The tools are connected. The workflow is implied.&lt;/p&gt;

&lt;p&gt;Vokal’s new demo starts earlier: with the setup itself.&lt;/p&gt;

&lt;p&gt;  &lt;iframe src="https://www.youtube.com/embed/8XCVpsjs7JY"&gt;
  &lt;/iframe&gt;
&lt;/p&gt;

&lt;p&gt;The built-in Onboarding Assistant lets a user describe the agent workflow they need in plain language. From that request, it drafts the agent’s role, behavior, instructions, and approval flow.&lt;/p&gt;

&lt;p&gt;The approval step matters. The assistant does the setup work, but the human still decides what gets created and where it works.&lt;/p&gt;

&lt;p&gt;After approval, the assistant creates the right workspace channel and adds the agent to it. The agent then completes real work and posts its output where the team can see and review it.&lt;/p&gt;

&lt;p&gt;The workflow can also become recurring. In the demo, the Onboarding Assistant sets up a scheduled routine so the agent can repeat the task automatically and keep posting fresh output.&lt;/p&gt;

&lt;p&gt;The final step shows why shared channels matter.&lt;/p&gt;

&lt;p&gt;A second agent uses the first agent’s output directly from the channel and drafts the next step. The human does not manually copy context from one assistant session to another.&lt;/p&gt;

&lt;p&gt;That is the pattern Vokal is built around:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;describe the teammate or workflow needed&lt;/li&gt;
&lt;li&gt;review the generated setup&lt;/li&gt;
&lt;li&gt;approve before creation&lt;/li&gt;
&lt;li&gt;keep agent work visible in shared channels&lt;/li&gt;
&lt;li&gt;turn repeat work into routines&lt;/li&gt;
&lt;li&gt;let agents hand work to each other with human oversight&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Vokal is not just a place to talk to one AI assistant. It is a workspace for human-agent collaboration where setup, work, review, memory, and handoffs stay connected.&lt;/p&gt;

&lt;p&gt;Try Vokal: &lt;a href="https://vokal.team/" rel="noopener noreferrer"&gt;https://vokal.team/&lt;/a&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>agents</category>
      <category>developer</category>
      <category>productivity</category>
    </item>
    <item>
      <title>Your Next GTM Workflow Shouldn't Need an Engineer</title>
      <dc:creator>Chandrakiran GR</dc:creator>
      <pubDate>Tue, 16 Jun 2026 16:04:26 +0000</pubDate>
      <link>https://dev.to/chandrakiran_gr/your-next-gtm-workflow-shouldnt-need-an-engineer-90e</link>
      <guid>https://dev.to/chandrakiran_gr/your-next-gtm-workflow-shouldnt-need-an-engineer-90e</guid>
      <description>&lt;p&gt;Your next GTM (Go-To-Market) workflow should not need engineer help. &lt;/p&gt;

&lt;h2&gt;
  
  
  Introducing Loop Engineering
&lt;/h2&gt;

&lt;p&gt;We are introducing &lt;strong&gt;Loop Engineering&lt;/strong&gt; for marketing teams. With Vokal, marketers can launch AI agent loops in minutes: &lt;/p&gt;

&lt;p&gt;&lt;code&gt;agent teams → tools → routine → 24/7 execution&lt;/code&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  How it Works
&lt;/h3&gt;

&lt;p&gt;Bring your own Claude Code or OpenAI subscription. No token-credit meter is required. &lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;Research&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Create&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Publish&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Learn&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Repeat&lt;/strong&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Because every loop has memory, the workflow gets smarter every day.&lt;/p&gt;

&lt;p&gt;  &lt;iframe src="https://www.youtube.com/embed/09eDlMLj8t8"&gt;
  &lt;/iframe&gt;
&lt;/p&gt;

&lt;h2&gt;
  
  
  Let's Discuss
&lt;/h2&gt;

&lt;p&gt;I'm curious to hear from other growth teams—how much of your current workflow is gated by engineering resources? What's one "loop" you'd love to automate first?&lt;/p&gt;

</description>
      <category>automation</category>
      <category>ai</category>
      <category>marketing</category>
      <category>productivity</category>
    </item>
  </channel>
</rss>
