<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Requirements on Keith Hodo</title><link>https://keithhodo.dev/tags/requirements/</link><description>Recent content in Requirements on Keith Hodo</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 Keith Hodo</copyright><lastBuildDate>Mon, 03 Aug 2026 17:02:57 -0700</lastBuildDate><atom:link href="https://keithhodo.dev/tags/requirements/index.xml" rel="self" type="application/rss+xml"/><item><title>Red to Green Proves Nothing: Formal Requirements Analysis in Kiro</title><link>https://keithhodo.dev/posts/requirements-analysis-agentic-clis/</link><pubDate>Mon, 03 Aug 2026 00:00:00 +0000</pubDate><guid>https://keithhodo.dev/posts/requirements-analysis-agentic-clis/</guid><description>A red-to-green test proves your code matches your test. It proves nothing about whether either one matches the product&amp;rsquo;s intent. Kiro can check requirements for contradictions with an SMT solver before any code exists, and I went through the documentation to find exactly where that capability lives and what it costs.</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://keithhodo.dev/posts/requirements-analysis-agentic-clis/feature.jpg"/></item></channel></rss>