<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Specifications on DevOpsTales</title>
    <link>https://devopstales.github.io/tags/specifications/</link>
    <description>Recent content in Specifications on DevOpsTales</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-US</language>
    <lastBuildDate>Mon, 21 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://devopstales.github.io/tags/specifications/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>What Is Spec-Driven Development? The Spec as Source of Truth</title>
      <link>https://devopstales.github.io/ai/what-is-spec-driven-development/</link>
      <pubDate>Mon, 21 Sep 2026 00:00:00 +0000</pubDate>
      
      <guid>https://devopstales.github.io/ai/what-is-spec-driven-development/</guid>
      <description>For most of software history the spec was a temporary planning artifact and the code was ground truth. Spec-driven development inverts that: the versioned specification becomes the primary artifact, and code is generated or verified against it. The idea is old — formal methods, design-by-contract, BDD all contain versions. What&rsquo;s new is the motive: AI agents need explicit, durable intent because prompts evaporate and sessions reset.
</description>
      <enclosure url="https://devopstales.github.io/img/what-is-spec-driven-development.webp" length="28404" type="image/png" />
    </item>
    
  </channel>
</rss>
