<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>AI4Kanban Blog</title>
    <link>https://ai4kanban.dev/blog</link>
    <description>Notes on planning and shipping software with coding agents, from the team behind AI4Kanban.</description>
    <language>en</language>
    <atom:link href="https://ai4kanban.dev/blog/rss.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Guardrails, specs and drafts: what each does for agent work</title>
      <link>https://ai4kanban.dev/blog/guardrails-specs-drafts</link>
      <guid>https://ai4kanban.dev/blog/guardrails-specs-drafts</guid>
      <description>The feature meets your requirements, but the UI looks awful. Guardrails set rules, specs define behavior, and drafts let you judge the actual screen before implementation.</description>
      <pubDate>Mon, 19 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>How we built an interactive demo of AI4Kanban with AI4Kanban</title>
      <link>https://ai4kanban.dev/blog/interactive-demo</link>
      <guid>https://ai4kanban.dev/blog/interactive-demo</guid>
      <description>AI4Kanban's UI drafts helped us catch problems before Claude Code built our interactive demo. We used no dedicated demo-building tools.</description>
      <pubDate>Wed, 14 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Draft-first development: rework the drafts, not the code</title>
      <link>https://ai4kanban.dev/blog/draft-first-development</link>
      <guid>https://ai4kanban.dev/blog/draft-first-development</guid>
      <description>A plan can describe a feature without showing whether it works as an idea. Draft-first development brings the key screens, copy and prompts into review before implementation.</description>
      <pubDate>Mon, 12 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Why spec-to-code fails, and how we fix it</title>
      <link>https://ai4kanban.dev/blog/spec-to-code</link>
      <guid>https://ai4kanban.dev/blog/spec-to-code</guid>
      <description>Spec-to-code fails when the spec is too long to review and too costly to change. We fix it by visualising what is hard to read, folding away what you need not read, and remembering what you decided.</description>
      <pubDate>Sat, 10 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Visual specs for AI coding: show me before you build</title>
      <link>https://ai4kanban.dev/blog/show-the-ui-first</link>
      <guid>https://ai4kanban.dev/blog/show-the-ui-first</guid>
      <description>A text plan makes you picture the feature before you can judge it. A visual spec shows the screen, so you can check it against what you want and let the agent build the rest.</description>
      <pubDate>Tue, 06 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>An AI kanban is not another dashboard</title>
      <link>https://ai4kanban.dev/blog/stop-watching-your-coding-agent</link>
      <guid>https://ai4kanban.dev/blog/stop-watching-your-coding-agent</guid>
      <description>An AI kanban coordinates task graphs, project memory, and agent decisions, then compresses the work into the few questions that need human judgment.</description>
      <pubDate>Mon, 31 Aug 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>How a PM harness tripled our development throughput</title>
      <link>https://ai4kanban.dev/blog/why-we-built-a-pm-harness</link>
      <guid>https://ai4kanban.dev/blog/why-we-built-a-pm-harness</guid>
      <description>AI4Kanban is a PM harness. In our own development work, it prepared tasks for coding agents, preserved product decisions, and asked for human judgment only when it mattered.</description>
      <pubDate>Fri, 21 Aug 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>What is Kanban Engineering—and why did we coin the term?</title>
      <link>https://ai4kanban.dev/blog/kanban-engineering</link>
      <guid>https://ai4kanban.dev/blog/kanban-engineering</guid>
      <description>Kanban Engineering is the planning layer around coding agents, connecting product goals to requirements, releases, and durable decisions.</description>
      <pubDate>Thu, 20 Aug 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Why project planning becomes the bottleneck with AI coding tools</title>
      <link>https://ai4kanban.dev/blog/project-decisions-are-the-bottleneck</link>
      <guid>https://ai4kanban.dev/blog/project-decisions-are-the-bottleneck</guid>
      <description>A codebase shows what was built, but it does not contain the full planning context behind the product. AI needs structured project memory to turn goals into well-scoped, correctly sequenced work.</description>
      <pubDate>Sat, 15 Aug 2026 00:00:00 GMT</pubDate>
    </item>
  </channel>
</rss>
