<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Matt Pocock on Top AI Skills</title><link>https://topaiskills.com/tags/matt-pocock/</link><description>Recent content in Matt Pocock on Top AI Skills</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 12 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://topaiskills.com/tags/matt-pocock/index.xml" rel="self" type="application/rss+xml"/><item><title>I Let AI Write My PRD for a Week Here's What Happened</title><link>https://topaiskills.com/tutorials/guides/to-prd-experiment/</link><pubDate>Fri, 12 Jun 2026 00:00:00 +0000</pubDate><guid>https://topaiskills.com/tutorials/guides/to-prd-experiment/</guid><description>&lt;h2 id="why-i-went-down-this-rabbit-hole"&gt;Why I Went Down This Rabbit Hole&lt;/h2&gt;
&lt;p&gt;It was a Tuesday afternoon, and I was staring at my third blank PRD template of the month. Same cursor blinking in the same &amp;ldquo;Problem Statement&amp;rdquo; field. Same feeling that I should be writing code instead of documenting why the code matters.&lt;/p&gt;
&lt;p&gt;I work on a small team. We ship fast, which means documentation is always the first thing to slip. PRDs end up as Notion scraps or Slack threads titled &amp;ldquo;that thing we discussed.&amp;rdquo; When I found &lt;code&gt;to-prd&lt;/code&gt; on skills.sh — described as a tool that synthesizes conversation context into a structured PRD and publishes it to your issue tracker — I installed it within 30 seconds. The promise was simple: stop writing requirements, start shipping. I&amp;rsquo;d already tried &lt;a href="https://topaiskills.com/skills/general/grill-me/"&gt;Grill Me&lt;/a&gt;, another Matt Pocock skill, for plan review. to-prd felt like the natural companion.&lt;/p&gt;</description></item></channel></rss>