<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Agentic Software Dev on Amir Hadifar</title>
    <link>https://hadifar.net/categories/agentic-software-dev/</link>
    <description>Recent content in Agentic Software Dev on Amir Hadifar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 20 Aug 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://hadifar.net/categories/agentic-software-dev/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Organize your skills</title>
      <link>https://hadifar.net/posts/organize-your-skills/</link>
      <pubDate>Thu, 20 Aug 2026 00:00:00 +0000</pubDate>
      <guid>https://hadifar.net/posts/organize-your-skills/</guid>
      <description>&lt;p&gt;A single &lt;code&gt;SKILL.md&lt;/code&gt; file is enough for personal use, but it doesn&amp;rsquo;t scale once you want to
version it, bundle it with agents and hooks, or share it with teammates. This post covers how
to package skills into a plugin and distribute that plugin through a marketplace.&lt;/p&gt;
&lt;p&gt;You probably don&amp;rsquo;t need plugins for a personal project or a quick one-off customization. You
do need them once you want to share with teammates, distribute to a community, cut versioned
releases, or reuse the same setup across projects.&lt;/p&gt;</description>
    </item>
    <item>
      <title>TDD for agents</title>
      <link>https://hadifar.net/posts/tdd-for-agents/</link>
      <pubDate>Thu, 06 Aug 2026 00:00:00 +0000</pubDate>
      <guid>https://hadifar.net/posts/tdd-for-agents/</guid>
      <description>&lt;p&gt;Many agentic workflows converge on the same shape: write a Markdown file at the root of your
repo, point your agent at it, and let it loop until it meets a stated goal. Test-driven
development is a natural fit for that shape — the tests &lt;em&gt;are&lt;/em&gt; the goal, and &amp;ldquo;all tests green&amp;rdquo;
is an unambiguous exit condition the agent can check without you.&lt;/p&gt;
&lt;h2 id=&#34;the-basic-loop&#34;&gt;The basic loop&lt;/h2&gt;
&lt;p&gt;In this paradigm you ask the agent to write tests first. You review them (or have another
agent review them), then ask the agent to implement the feature until every test passes.
You revise the tests a little, the agent revises the code a little, and when everything is
green you move to the next feature — with a fully testable one behind you.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Gstack: AI engineering workflow</title>
      <link>https://hadifar.net/posts/gstack-ai-engineering-workflow/</link>
      <pubDate>Fri, 31 Jul 2026 00:00:00 +0000</pubDate>
      <guid>https://hadifar.net/posts/gstack-ai-engineering-workflow/</guid>
      <description>&lt;p&gt;This post explains the AI coding workflow of Y Combinator&amp;rsquo;s CEO — how he uses &lt;a href=&#34;https://github.com/garrytan/gstack.git&#34;&gt;GStack&lt;/a&gt; for ideation, building, and deployment.&lt;/p&gt;
&lt;h2 id=&#34;what-is-gstack&#34;&gt;What is gstack&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;gstack&lt;/strong&gt; is a collection of &lt;code&gt;SKILL.md&lt;/code&gt; files that give your AI agents personas for different stages of the
software/product development life cycle.&lt;/p&gt;
&lt;p&gt;A normal software sprint runs through roughly these stages:&lt;/p&gt;
&lt;div class=&#34;highlight&#34;&gt;&lt;div class=&#34;chroma&#34;&gt;
&lt;table class=&#34;lntable&#34;&gt;&lt;tr&gt;&lt;td class=&#34;lntd&#34;&gt;
&lt;pre tabindex=&#34;0&#34; class=&#34;chroma&#34;&gt;&lt;code&gt;&lt;span class=&#34;lnt&#34;&gt;1
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/td&gt;
&lt;td class=&#34;lntd&#34;&gt;
&lt;pre tabindex=&#34;0&#34; class=&#34;chroma&#34;&gt;&lt;code class=&#34;language-text&#34; data-lang=&#34;text&#34;&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;think → plan → design → build → review → test → ship
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;
&lt;/div&gt;
&lt;/div&gt;&lt;p&gt;In gstack, there is a &lt;code&gt;SKILL.md&lt;/code&gt; file (often several) for each of these stages. You invoke
them to guide your agents toward the goal (generating code, a specification, ideation, etc.).&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
