<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Spec-Kit on DevOpsTales</title>
    <link>https://devopstales.github.io/tags/spec-kit/</link>
    <description>Recent content in Spec-Kit on DevOpsTales</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-US</language>
    <lastBuildDate>Thu, 20 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://devopstales.github.io/tags/spec-kit/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Spec Kit vs Kiro vs Claude Code: Picking an SDD Setup by Tradeoff, Not Hype</title>
      <link>https://devopstales.github.io/ai/spec-kit-kiro-claude-code-sdd/</link>
      <pubDate>Thu, 20 Aug 2026 00:00:00 +0000</pubDate>
      
      <guid>https://devopstales.github.io/ai/spec-kit-kiro-claude-code-sdd/</guid>
      <description>Developers comparing spec-driven setups in 2026 usually aren&rsquo;t asking which model is smartest. They&rsquo;re asking which workflow keeps an AI agent aligned without burying them in ceremony. Spec Kit, Kiro, and Claude Code custom workflows all implement specify-plan-tasks-implement-validate — but they bet differently on portability versus integration depth.
</description>
      <enclosure url="https://devopstales.github.io/img/sdd-tooling-comparison-icon.webp" length="9708" type="image/png" />
    </item>
    
  </channel>
</rss>
