<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>The inplan blog</title>
    <link>https://inplan.ai/blog.html</link>
    <atom:link href="https://inplan.ai/feed.xml" rel="self" type="application/rss+xml" />
    <description>Writing on planning-driven development, agentic coding, and building with a coding agent — from the team behind inplan.</description>
    <language>en</language>
    <lastBuildDate>Mon, 20 Jul 2026 13:00:00 GMT</lastBuildDate>

    <item>
      <title>Engineer the loop, not the prompt</title>
      <link>https://inplan.ai/blog/engineer-the-loop.html</link>
      <guid isPermaLink="true">https://inplan.ai/blog/engineer-the-loop.html</guid>
      <pubDate>Thu, 16 Jul 2026 13:00:00 GMT</pubDate>
      <description>Loop engineering says the unit you optimize is the loop, not the prompt. But Andrew Ng's developer feedback loop — where judgment becomes specs and evaluation criteria — is exactly what a plan is: the loop's memory, validation, and exit conditions, kept alive against drift.</description>
    </item>

    <item>
      <title>A one-liner builds the minimum. A plan builds the app.</title>
      <link>https://inplan.ai/blog/build-off-with-a-plan.html</link>
      <guid isPermaLink="true">https://inplan.ai/blog/build-off-with-a-plan.html</guid>
      <pubDate>Fri, 10 Jul 2026 13:00:00 GMT</pubDate>
      <description>We re-ran all four of the build-off's apps — calculator, Conway's Life, Rubik's cube, raycaster — same model, one-liner vs a plan that spells out the real feature set, with the plan and the rubric written double-blind. The one-liner delivered 11–67% of the app; the plan delivered 63–91%.</description>
    </item>

    <item>
      <title>A plan for the page</title>
      <link>https://inplan.ai/blog/a-plan-for-the-page.html</link>
      <guid isPermaLink="true">https://inplan.ai/blog/a-plan-for-the-page.html</guid>
      <pubDate>Fri, 10 Jul 2026 13:00:00 GMT</pubDate>
      <description>Planning-first isn't only for code. A novelist, an investigative reporter, and a game's narrative designer use the same shared document — an AI drafts and raises open questions in parallel threads, and they decide in place before committing to the page.</description>
    </item>

    <item>
      <title>One document, three jobs</title>
      <link>https://inplan.ai/blog/how-teams-use-inplan.html</link>
      <guid isPermaLink="true">https://inplan.ai/blog/how-teams-use-inplan.html</guid>
      <pubDate>Fri, 03 Jul 2026 13:00:00 GMT</pubDate>
      <description>A developer, a product manager, and an architect work the same planning document three different ways — settling the implementation, product, and structural questions before a coding agent writes a line. Three concrete stories.</description>
    </item>

    <item>
      <title>All you need is more thorough planning</title>
      <link>https://inplan.ai/blog/does-planning-make-your-agent-faster.html</link>
      <guid isPermaLink="true">https://inplan.ai/blog/does-planning-make-your-agent-faster.html</guid>
      <pubDate>Fri, 26 Jun 2026 13:00:00 GMT</pubDate>
      <description>Coding agents write fast and guess wrong — quietly. We put it to the test on a checkout pricing engine: same prompt, same agent, first-pass correctness went from 4/8 to 8/8. Why planning first is how you ship it right, and about 30% faster overall.</description>
    </item>

    <item>
      <title>Your coding agent doesn't need a better model. It needs a better plan.</title>
      <link>https://inplan.ai/blog/planning-in-agentic-coding.html</link>
      <guid isPermaLink="true">https://inplan.ai/blog/planning-in-agentic-coding.html</guid>
      <pubDate>Fri, 19 Jun 2026 13:00:00 GMT</pubDate>
      <description>Agentic coding's real bottleneck isn't the model — it's shared understanding. Why planning is the highest-leverage thing you can do with a coding agent, and what "planning" actually means in this era.</description>
    </item>
  </channel>
</rss>
