<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Spec Writing on Top AI Skills</title><link>https://topaiskills.com/tags/spec-writing/</link><description>Recent content in Spec Writing on Top AI Skills</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 24 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://topaiskills.com/tags/spec-writing/index.xml" rel="self" type="application/rss+xml"/><item><title>My Spec Session With to-Spec: No Interview, Just Synthesis</title><link>https://topaiskills.com/tutorials/guides/to-spec-narrative-experience/</link><pubDate>Mon, 24 Aug 2026 00:00:00 +0000</pubDate><guid>https://topaiskills.com/tutorials/guides/to-spec-narrative-experience/</guid><description>&lt;p&gt;I came to Matt Pocock&amp;rsquo;s to-spec skill expecting twenty questions. It turned me down flat. The skill — skills.sh #122 with 361,627 installs, from the &lt;a href="https://github.com/mattpocock/skills" rel="nofollow" target="_blank"&gt;mattpocock/skills&lt;/a&gt; repo (235K stars) — states its contract in nine words: &amp;ldquo;no interview, just synthesis of what you&amp;rsquo;ve already discussed.&amp;rdquo; Its frontmatter carries &lt;code&gt;disable-model-invocation: true&lt;/code&gt;, so nothing triggers it by accident. I invoked it on a half-formed checkout change with a messy chat history behind it, and watched it turn that mess into a published spec. Here&amp;rsquo;s what the session actually looked like, including the parts where the skill refused to do what I expected.&lt;/p&gt;</description></item></channel></rss>