<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: natedaines</title><link>https://news.ycombinator.com/user?id=natedaines</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Fri, 17 Apr 2026 14:16:35 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=natedaines" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[Show HN: Simple spec driven development for Claude]]></title><description><![CDATA[
<p>Article URL: <a href="https://tinyspec.dev/">https://tinyspec.dev/</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=47306361">https://news.ycombinator.com/item?id=47306361</a></p>
<p>Points: 1</p>
<p># Comments: 0</p>
]]></description><pubDate>Mon, 09 Mar 2026 08:49:23 +0000</pubDate><link>https://tinyspec.dev/</link><dc:creator>natedaines</dc:creator><comments>https://news.ycombinator.com/item?id=47306361</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47306361</guid></item><item><title><![CDATA[New comment by natedaines in "Ask HN: What Are You Working On? (March 2026)"]]></title><description><![CDATA[
<p>I was exploring a spec development system (similar to the likes of openspec) but with specifications that are more succinct. One of my frustration with openspec is the number of files that are generated from the proposal, to the design and implementation.<p><a href="https://tinyspec.dev/" rel="nofollow">https://tinyspec.dev/</a></p>
]]></description><pubDate>Mon, 09 Mar 2026 07:58:51 +0000</pubDate><link>https://news.ycombinator.com/item?id=47306024</link><dc:creator>natedaines</dc:creator><comments>https://news.ycombinator.com/item?id=47306024</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47306024</guid></item><item><title><![CDATA[New comment by natedaines in "Handover.ai – Knowledge transfer made easy"]]></title><description><![CDATA[
<p>I'd love to be able to use this tool to write documentation that may not be specific to a "handover".<p>I find it hard to know where to start, what to include and how to structure. Having a tool to prompt me along the way would be really helpful and I feel speed up the process of ideation and creation of documentation.</p>
]]></description><pubDate>Thu, 29 May 2025 04:55:18 +0000</pubDate><link>https://news.ycombinator.com/item?id=44123247</link><dc:creator>natedaines</dc:creator><comments>https://news.ycombinator.com/item?id=44123247</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=44123247</guid></item><item><title><![CDATA[New comment by natedaines in "Show HN: Handover.ai – Knowledge transfer made easy"]]></title><description><![CDATA[
<p>I imagine there would be a benefit if they are using an llm to understand key pieces of information (such as we use kubernetes); it could then just know what questions should be asked around that subject area to ensure enough details are captured as part of a handover. I can imagine it as being a template but on steroids.</p>
]]></description><pubDate>Thu, 29 May 2025 04:48:49 +0000</pubDate><link>https://news.ycombinator.com/item?id=44123220</link><dc:creator>natedaines</dc:creator><comments>https://news.ycombinator.com/item?id=44123220</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=44123220</guid></item></channel></rss>