<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Product-Requirements on David R. Longnecker - Converting Coffee to Code</title><link>https://drlongnecker.com/tags/product-requirements/</link><description>Recent content in Product-Requirements on David R. Longnecker - Converting Coffee to Code</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 04 Aug 2026 09:00:00 -0600</lastBuildDate><atom:link href="https://drlongnecker.com/tags/product-requirements/index.xml" rel="self" type="application/rss+xml"/><item><title>The Same Discipline, One Layer Deeper</title><link>https://drlongnecker.com/blog/2026/08/spec-driven-development-product-work-hoodie/</link><pubDate>Tue, 04 Aug 2026 09:00:00 -0600</pubDate><guid>https://drlongnecker.com/blog/2026/08/spec-driven-development-product-work-hoodie/</guid><description>&lt;p&gt;&lt;em&gt;This is Part 3 of a three-part series on what changes when agents, not just people, become your product&amp;rsquo;s clients: &lt;a href="https://drlongnecker.com/blog/2026/04/agent-facing-product-design-api-first-interface"&gt;The New Front Door&lt;/a&gt; · &lt;a href="https://drlongnecker.com/blog/2026/07/governing-pm-ai-accountability-product-management"&gt;The Governing PM&lt;/a&gt; · &lt;strong&gt;The Same Discipline, One Layer Deeper&lt;/strong&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Engineering blogs are currently rediscovering a discipline product managers have practiced imperfectly for two decades: write down what &amp;ldquo;done&amp;rdquo; and &amp;ldquo;correct&amp;rdquo; mean before work starts, or ambiguity gets resolved badly and expensively later. They&amp;rsquo;re calling it spec-driven development. Part of what they&amp;rsquo;re describing, I&amp;rsquo;ve been calling Tuesday.&lt;/p&gt;</description></item></channel></rss>