<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Engineering Workflow on Top AI Skills</title><link>https://topaiskills.com/tags/engineering-workflow/</link><description>Recent content in Engineering Workflow on Top AI Skills</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 20 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://topaiskills.com/tags/engineering-workflow/index.xml" rel="self" type="application/rss+xml"/><item><title>Prototype vs TDD: When to Explore Throwaway and When to Go Test-First</title><link>https://topaiskills.com/tutorials/comparison/prototype-vs-tdd-comparison/</link><pubDate>Thu, 20 Aug 2026 00:00:00 +0000</pubDate><guid>https://topaiskills.com/tutorials/comparison/prototype-vs-tdd-comparison/</guid><description>&lt;p&gt;The same idea can be built two radically different ways inside the Matt Pocock skills family, and picking wrong wastes a day. &lt;a href="https://topaiskills.com/skills/general/prototype/"&gt;Prototype&lt;/a&gt; makes you write throwaway code that answers one question and then throw it away. &lt;a href="https://topaiskills.com/tutorials/guides/i-tried-tdd-with-an-ai-assistant/"&gt;TDD&lt;/a&gt; makes you lock behavior down test-first, from the first line. Both live in &lt;a href="https://github.com/mattpocock/skills" rel="nofollow" target="_blank"&gt;mattpocock/skills&lt;/a&gt; (223K stars), both rank in the top ~15 on skills.sh, and both solve &amp;ldquo;turn an idea into code&amp;rdquo; — but they&amp;rsquo;re built for opposite moments. I read the actual SKILL.md files for prototype, tdd, to-spec, implement, and code-review, and the boundary between them is sharper than the descriptions suggest.&lt;/p&gt;</description></item></channel></rss>