<?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>Tech Spec on Chuanxilu for Skilled Homo sapiens</title><link>https://blog.chuanxilu.net/en/tags/tech-spec/</link><description>Recent content in Tech Spec on Chuanxilu for Skilled Homo sapiens</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Wed, 29 Apr 2026 10:00:00 +0800</lastBuildDate><atom:link href="https://blog.chuanxilu.net/en/tags/tech-spec/index.xml" rel="self" type="application/rss+xml"/><item><title>Why PRD Alone Is Not Enough: What the Tech Spec Must Cover in AI-Assisted Development</title><link>https://blog.chuanxilu.net/en/posts/2026/04/prd-to-tech-spec-ai-design-guardrails/</link><pubDate>Wed, 29 Apr 2026 10:00:00 +0800</pubDate><guid>https://blog.chuanxilu.net/en/posts/2026/04/prd-to-tech-spec-ai-design-guardrails/</guid><description>The second Aristotle refactor had clear requirements, clean code structure, passing tests. But the async background mechanism still did not work. The problem was not in the PRD; it was in the tech spec. This article covers what a PRD should contain, what a tech spec should add, and why both are non-negotiable when AI writes your code.</description></item></channel></rss>