<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>coding-agent on My learning and diary</title>
    <link>https://jackliusr.github.io/tags/coding-agent/</link>
    <description>Recent content in coding-agent on My learning and diary</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 12 May 2026 20:00:00 +0800</lastBuildDate><atom:link href="https://jackliusr.github.io/tags/coding-agent/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Reducing Architecture Drift in Spec-Driven Development with coding agents and LLMs</title>
      <link>https://jackliusr.github.io/posts/2026/05/reducing-architecture-drift-in-spec-driven-development-with-coding-agents-and-llms/</link>
      <pubDate>Tue, 12 May 2026 20:00:00 +0800</pubDate>
      
      <guid>https://jackliusr.github.io/posts/2026/05/reducing-architecture-drift-in-spec-driven-development-with-coding-agents-and-llms/</guid>
      <description>Introduction Spec-driven development is becoming increasingly popular in the era of AI-assisted software engineering. Instead of starting directly from implementation, teams define specifications, domain rules, contracts, and architectural intentions first, allowing Large Language Models (LLMs) and automation tools to generate significant parts of the system.
 This approach can dramatically improve development speed, documentation quality, and alignment between business and engineering.
 However, one important challenge emerges quickly:
  Architecture drift.</description>
    </item>
    
  </channel>
</rss>
