<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>PRD on ByF (BaiFan) · Daily Deep Think</title><link>https://blog.baifan.site/en/tags/prd/</link><description>Recent content in PRD on ByF (BaiFan) · Daily Deep Think</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>blog@baifan.site (ByF (BaiFan))</managingEditor><webMaster>blog@baifan.site (ByF (BaiFan))</webMaster><copyright>CC BY-NC 4.0</copyright><lastBuildDate>Wed, 05 Aug 2026 14:28:39 +0800</lastBuildDate><atom:link href="https://blog.baifan.site/en/tags/prd/index.xml" rel="self" type="application/rss+xml"/><item><title>Give AI a Rulebook: From Wishing Upon It to Making It Behave</title><link>https://blog.baifan.site/en/give-ai-a-rulebook/</link><pubDate>Wed, 05 Aug 2026 14:28:39 +0800</pubDate><author>blog@baifan.site (ByF (BaiFan))</author><guid>https://blog.baifan.site/en/give-ai-a-rulebook/</guid><description>&lt;p&gt;Let me start with something that actually happened.&lt;/p&gt;&#10;&lt;p&gt;In early 2025, I added a feature to an internal system: export to Excel. Small requirement — I didn&amp;rsquo;t even write it up, just typed &amp;ldquo;add an export button to the list page&amp;rdquo; into the chat box.&lt;/p&gt;&#10;&lt;p&gt;The AI delivered in ten minutes. Frontend changes, new endpoint, SQL — all in one pass. I was pleased when I opened the PR, right up until review revealed: the export columns didn&amp;rsquo;t match the list page, a hundred thousand rows would hang the service outright, there was no permission check, and the tests only covered the happy path.&lt;/p&gt;</description></item><item><title>A New Playbook for AI Programming: UI First, Then the PRD</title><link>https://blog.baifan.site/en/ui-first-ai-programming-prd/</link><pubDate>Tue, 17 Feb 2026 14:00:00 +0800</pubDate><author>blog@baifan.site (ByF (BaiFan))</author><guid>https://blog.baifan.site/en/ui-first-ai-programming-prd/</guid><description>&lt;!-- more --&gt;&#10;&lt;p&gt;Everyone knows the standard Vibe Coding flow by now: write user stories → produce a PRD → AI generates the backend → AI generates the frontend → demo and verify. It works, but at delivery time the UI interaction experience often falls far short of expectations. Where does it go wrong? In the PRD itself.&lt;/p&gt;&#10;&#10;&lt;h2 class="relative group"&gt;1. The Fundamental Problem with PRDs&#10; &lt;div id="1-the-fundamental-problem-with-prds" class="anchor"&gt;&lt;/div&gt;&#10; &#10; &lt;span&#10; class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"&gt;&#10; &lt;a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#1-the-fundamental-problem-with-prds" aria-label="Anchor"&gt;#&lt;/a&gt;&#10; &lt;/span&gt;&#10; &#10;&lt;/h2&gt;&#10;&lt;p&gt;PRDs (Product Requirements Documents) were never that friendly to humans in the first place. Three reasons:&lt;/p&gt;</description></item></channel></rss>