<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>AI Coding on Human in the Loop</title><link>http://aitip.tech/en/tags/ai-coding/</link><description>Recent content in AI Coding on Human in the Loop</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Tue, 17 Nov 2026 09:00:00 +0800</lastBuildDate><atom:link href="http://aitip.tech/en/tags/ai-coding/index.xml" rel="self" type="application/rss+xml"/><item><title>AI Spec-Driven Development: Why We Chose OpenSpec</title><link>http://aitip.tech/en/posts/openspec-spec-driven/</link><pubDate>Tue, 17 Nov 2026 09:00:00 +0800</pubDate><guid>http://aitip.tech/en/posts/openspec-spec-driven/</guid><description>When you code with AI, requirements live only in chat history and vanish with the next session. Spec-driven development puts them in the repo, but Spec Kit, Kiro and Tessl take very different approaches, and critics call it waterfall coming back. This post compares the main tools against the industry critiques, explains why we chose OpenSpec, and shares the practices we built up over a dozen-plus repos and more than a hundred changes.</description></item></channel></rss>