<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Spec-Driven on Vibe Coding</title><link>https://vibecoding.rest/tags/spec-driven/</link><description>Recent content in Spec-Driven on Vibe Coding</description><generator>Hugo</generator><language>en</language><atom:link href="https://vibecoding.rest/tags/spec-driven/index.xml" rel="self" type="application/rss+xml"/><item><title>Kiro</title><link>https://vibecoding.rest/tools/kiro/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/tools/kiro/</guid><description>&lt;p&gt;Kiro is AWS&amp;rsquo;s agentic IDE, built around &amp;ldquo;spec-driven development&amp;rdquo;: instead of jumping straight from a prompt to code, it first produces a written specification and task breakdown for you to review, then implements against that spec — a departure from AWS&amp;rsquo;s usual approach of tying developer tools tightly to its own cloud services, since Kiro is cloud-agnostic.&lt;/p&gt;</description></item><item><title>Get Shit Done</title><link>https://vibecoding.rest/skills/get-shit-done/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/get-shit-done/</guid><description>&lt;p&gt;Get Shit Done is a lightweight meta-prompting and context-engineering system for Claude Code, built around spec-driven development rather than ad hoc prompting.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;Spec-first workflows tend to produce more predictable output than freeform prompting, especially on larger features. Packaging that discipline as a skill makes it the default instead of something re-explained per task.&lt;/p&gt;</description></item></channel></rss>