<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Entalpa guides</title>
    <link>https://entalpa.com/en/guides</link>
    <atom:link href="https://entalpa.com/feed.xml" rel="self" type="application/rss+xml" />
    <description>Long-form pieces on spec-driven development for AI coding agents, built from what developers said about their own projects and from incidents in ours.</description>
    <language>en</language>
    <item>
      <title>A PRD template your coding agent can actually follow</title>
      <link>https://entalpa.com/en/guides/prd-template</link>
      <guid isPermaLink="true">https://entalpa.com/en/guides/prd-template</guid>
      <pubDate>Fri, 25 Sep 2026 00:00:00 GMT</pubDate>
      <description>A product requirements document template written for the agent that reads it: requirement IDs, testable acceptance criteria, explicit out-of-scope, and open questions that stop the build. Copy it, fill it, hand it to Claude Code, Cursor or Codex.</description>
    </item>
    <item>
      <title>Spec-driven development with Claude Code</title>
      <link>https://entalpa.com/en/guides/spec-driven-development-with-claude-code</link>
      <guid isPermaLink="true">https://entalpa.com/en/guides/spec-driven-development-with-claude-code</guid>
      <pubDate>Tue, 15 Sep 2026 00:00:00 GMT</pubDate>
      <description>What Claude Code already gives you for building from a spec (CLAUDE.md, plan mode, MCP), the lightest loop that is actually spec-driven, the three places it breaks, and how to hand Claude Code a spec it cannot rewrite.</description>
    </item>
    <item>
      <title>Spec-driven development, and what happened to it</title>
      <link>https://entalpa.com/en/guides/spec-driven-development</link>
      <guid isPermaLink="true">https://entalpa.com/en/guides/spec-driven-development</guid>
      <pubDate>Tue, 15 Sep 2026 00:00:00 GMT</pubDate>
      <description>Spec-driven development, defined in one paragraph; the tools that carry it; the two Ask HN threads asking whether anyone still does it; and the one complaint that outlived the hype: the agent still builds things that are not in the spec.</description>
    </item>
    <item>
      <title>Your agent is not a yes-man — your prompt is missing a spec</title>
      <link>https://entalpa.com/en/guides/agent-guesses-requirements</link>
      <guid isPermaLink="true">https://entalpa.com/en/guides/agent-guesses-requirements</guid>
      <pubDate>Mon, 31 Aug 2026 00:00:00 GMT</pubDate>
      <description>Agents get called sycophantic for agreeing with everything and shipping the wrong feature. The failure is not agreeableness — a model cannot object to a constraint nobody stated, so it fills the hole with the most typical answer.</description>
    </item>
    <item>
      <title>Nobody reviews a 2,000-line AI diff</title>
      <link>https://entalpa.com/en/guides/reviewing-the-spec-not-the-diff</link>
      <guid isPermaLink="true">https://entalpa.com/en/guides/reviewing-the-spec-not-the-diff</guid>
      <pubDate>Mon, 31 Aug 2026 00:00:00 GMT</pubDate>
      <description>45% of developers say debugging AI code takes longer than writing it. Generation sped up 100x; reading unfamiliar code did not speed up at all. The reviewable unit has to move upstream of the diff.</description>
    </item>
    <item>
      <title>Your agent will &quot;fix&quot; the thing you did on purpose</title>
      <link>https://entalpa.com/en/guides/what-your-agent-breaks</link>
      <guid isPermaLink="true">https://entalpa.com/en/guides/what-your-agent-breaks</guid>
      <pubDate>Mon, 31 Aug 2026 00:00:00 GMT</pubDate>
      <description>An agent sent to fix a bug in our own repository standardised behaviour that was deliberately non-standard, because nothing recorded that it was deliberate. What that failure actually is, and what stops it.</description>
    </item>
    <item>
      <title>The vibe-coding wall, in five people's words</title>
      <link>https://entalpa.com/en/guides/the-vibe-coding-wall</link>
      <guid isPermaLink="true">https://entalpa.com/en/guides/the-vibe-coding-wall</guid>
      <pubDate>Mon, 31 Aug 2026 00:00:00 GMT</pubDate>
      <description>Vibe coding is excellent at the prototype and bad at the second month. Five specific ways it breaks, quoted from developers describing their own projects, and what genuinely helps against each one.</description>
    </item>
  </channel>
</rss>
