<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Specifications on Fernando Ruiz</title><link>https://www.fernandoux.com/tags/specifications/</link><description>Recent content in Specifications on Fernando Ruiz</description><generator>Hugo</generator><language>en-us</language><atom:link href="https://www.fernandoux.com/tags/specifications/index.xml" rel="self" type="application/rss+xml"/><item><title>Spec-driven development: the specification first, then the code</title><link>https://www.fernandoux.com/en/wiki/ai/spec-driven-development/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://www.fernandoux.com/en/wiki/ai/spec-driven-development/</guid><description>&lt;div class="info-panel"&gt;
 &lt;div class="info-header"&gt;
 &lt;span class="material-symbols-outlined info-panel-icon"&gt;info&lt;/span&gt;
 &lt;span class="info-panel-label"&gt;Quick Definition&lt;/span&gt;
 &lt;/div&gt;
 &lt;div class="info-content"&gt;
 &lt;strong&gt;Spec-driven development&lt;/strong&gt; is a workflow in which you write a specification before the AI generates code, and that specification becomes the project&amp;rsquo;s source of truth: what is being built, for whom and with which success criteria.
 &lt;/div&gt;
&lt;/div&gt;

&lt;h2 id="what-problem-does-it-try-to-solve"&gt;What problem does it try to solve?&lt;/h2&gt;
&lt;p&gt;[[what-is-vibe-coding|Vibe coding]], where you describe an idea loosely and accept the result, has a drift problem. In each session the AI can make new decisions: rename something, invent an architecture or forget a rule from the previous session. Without a document that fixes them, nobody knows what was decided or why.&lt;/p&gt;</description></item></channel></rss>