<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Traceability on DevOpsTales</title>
    <link>https://devopstales.github.io/tags/traceability/</link>
    <description>Recent content in Traceability on DevOpsTales</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-US</language>
    <lastBuildDate>Thu, 27 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://devopstales.github.io/tags/traceability/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Keeping Specs, Tests, and Code in Sync When Agents Write Fast</title>
      <link>https://devopstales.github.io/ai/spec-test-code-traceability/</link>
      <pubDate>Thu, 27 Aug 2026 00:00:00 +0000</pubDate>
      
      <guid>https://devopstales.github.io/ai/spec-test-code-traceability/</guid>
      <description>A spec nobody re-checks against the running system is worse than no spec: reviewers trust the document instead of the diff while the agent follows whatever the code actually does. Agents regenerate code fast, and each regeneration is a fresh chance for spec and implementation to diverge. The fix is a small enforceable link between requirement, design decision, tests, and the commits that changed them.
</description>
      <enclosure url="https://devopstales.github.io/img/spec-test-code-traceability-icon.webp" length="4894" type="image/png" />
    </item>
    
  </channel>
</rss>
