<?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>Requirements Engineering on Chuanxilu for Skilled Homo sapiens</title><link>https://blog.chuanxilu.net/en/tags/requirements-engineering/</link><description>Recent content in Requirements Engineering on Chuanxilu for Skilled Homo sapiens</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Sat, 25 Apr 2026 00:00:00 +0800</lastBuildDate><atom:link href="https://blog.chuanxilu.net/en/tags/requirements-engineering/index.xml" rel="self" type="application/rss+xml"/><item><title>Why AI-Assisted Development Needs Structured Requirements First: Lessons from the GEAR Protocol</title><link>https://blog.chuanxilu.net/en/posts/2026/04/why-aristotle-vibe-development-needs-gear-protocol/</link><pubDate>Sat, 25 Apr 2026 00:00:00 +0800</pubDate><guid>https://blog.chuanxilu.net/en/posts/2026/04/why-aristotle-vibe-development-needs-gear-protocol/</guid><description>Aristotle v1 had a one-line requirement. The reflection task ran inside the main session, polluting 371 lines of context. This article starts from that failure and walks through why requirement gaps get amplified into systematic bias in AI-assisted development, and how structured methods close those gaps.</description></item></channel></rss>