<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Laimonade blog</title>
    <link>https://laimonade.com/blog</link>
    <description>Notes on product ownership for teams running coding agents.</description>
    <language>en</language>
    <atom:link href="https://laimonade.com/rss.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Coding agent security: what can it reach?</title>
      <link>https://laimonade.com/blog/is-it-safe-to-let-coding-agents-into-your-backlog</link>
      <guid isPermaLink="true">https://laimonade.com/blog/is-it-safe-to-let-coding-agents-into-your-backlog</guid>
      <pubDate>Fri, 25 Sep 2026 00:00:00 GMT</pubDate>
      <description>Coding agent security is a question about capability, not intention. Judge a connection by what it cannot reach, not by what a vendor promises.</description>
    </item>
    <item>
      <title>Agent permissions: what should you grant?</title>
      <link>https://laimonade.com/blog/what-permissions-should-a-coding-agent-have</link>
      <guid isPermaLink="true">https://laimonade.com/blog/what-permissions-should-a-coding-agent-have</guid>
      <pubDate>Fri, 25 Sep 2026 00:00:00 GMT</pubDate>
      <description>Agent permissions come down to one line: enough to fetch work and hand it back, and no authority to close it. Where that line sits, and how to review it.</description>
    </item>
    <item>
      <title>Backlog migration without losing what makes it work</title>
      <link>https://laimonade.com/blog/migrating-a-backlog-without-losing-context</link>
      <guid isPermaLink="true">https://laimonade.com/blog/migrating-a-backlog-without-losing-context</guid>
      <pubDate>Thu, 24 Sep 2026 00:00:00 GMT</pubDate>
      <description>A backlog migration that imports everything moves rows and loses reasons. Migrate the next two sprints properly and leave the archive where it is.</description>
    </item>
    <item>
      <title>Solo founder coding agents: shipping a product alone</title>
      <link>https://laimonade.com/blog/running-a-product-single-handed-with-coding-agents</link>
      <guid isPermaLink="true">https://laimonade.com/blog/running-a-product-single-handed-with-coding-agents</guid>
      <pubDate>Thu, 24 Sep 2026 00:00:00 GMT</pubDate>
      <description>Solo founder coding agents do not remove a job, they collapse two. You are the product owner and the reviewer, and both want the same hour every day.</description>
    </item>
    <item>
      <title>Connect Claude Code to backlog items over MCP</title>
      <link>https://laimonade.com/blog/connecting-claude-code-to-your-backlog</link>
      <guid isPermaLink="true">https://laimonade.com/blog/connecting-claude-code-to-your-backlog</guid>
      <pubDate>Wed, 23 Sep 2026 00:00:00 GMT</pubDate>
      <description>One command, one authorisation, and you connect Claude Code to backlog items it can fetch itself — with criteria attached. Plus what to do when it drops.</description>
    </item>
    <item>
      <title>What to look for in an agent-native project tracker</title>
      <link>https://laimonade.com/blog/what-to-look-for-in-an-agent-native-project-tracker</link>
      <guid isPermaLink="true">https://laimonade.com/blog/what-to-look-for-in-an-agent-native-project-tracker</guid>
      <pubDate>Wed, 23 Sep 2026 00:00:00 GMT</pubDate>
      <description>An AI feature bolted onto a tracker is not an agent-native project tracker. Four capabilities that decide it, and the ones that turn out not to.</description>
    </item>
    <item>
      <title>An engineering audit of what your agents actually shipped</title>
      <link>https://laimonade.com/blog/auditing-what-your-agents-actually-shipped</link>
      <guid isPermaLink="true">https://laimonade.com/blog/auditing-what-your-agents-actually-shipped</guid>
      <pubDate>Tue, 22 Sep 2026 00:00:00 GMT</pubDate>
      <description>An engineering audit compares three lists: items marked done, commits merged, and behaviour a user can observe. Work in only one of them is the finding.</description>
    </item>
    <item>
      <title>Jira alternatives when an agent reads your backlog</title>
      <link>https://laimonade.com/blog/jira-alternatives-for-teams-running-coding-agents</link>
      <guid isPermaLink="true">https://laimonade.com/blog/jira-alternatives-for-teams-running-coding-agents</guid>
      <pubDate>Tue, 22 Sep 2026 00:00:00 GMT</pubDate>
      <description>The usual Jira alternatives differ in speed and taste, not in kind. What to test a tracker for when the thing reading your backlog is a coding agent.</description>
    </item>
    <item>
      <title>Quality gates that fail quietly, and how to find yours</title>
      <link>https://laimonade.com/blog/quality-gates-that-fail-quietly</link>
      <guid isPermaLink="true">https://laimonade.com/blog/quality-gates-that-fail-quietly</guid>
      <pubDate>Mon, 21 Sep 2026 00:00:00 GMT</pubDate>
      <description>Quality gates fail quietly when they exit zero for a reason unrelated to what they check. Four patterns, and how to prove yours is not one of them.</description>
    </item>
    <item>
      <title>Agent evidence: what should come back with the work?</title>
      <link>https://laimonade.com/blog/what-evidence-should-a-coding-agent-return</link>
      <guid isPermaLink="true">https://laimonade.com/blog/what-evidence-should-a-coding-agent-return</guid>
      <pubDate>Mon, 21 Sep 2026 00:00:00 GMT</pubDate>
      <description>Agent evidence is what a reviewer can re-run: the commands and their exit codes, the files changed, and the criterion each change satisfies.</description>
    </item>
    <item>
      <title>Sprint length for teams running coding agents</title>
      <link>https://laimonade.com/blog/sprint-length-for-teams-running-agents</link>
      <guid isPermaLink="true">https://laimonade.com/blog/sprint-length-for-teams-running-agents</guid>
      <pubDate>Sun, 20 Sep 2026 00:00:00 GMT</pubDate>
      <description>Sprint length should be the larger of two numbers, and coding agents collapse one of them while leaving the other exactly where it was.</description>
    </item>
    <item>
      <title>Status accuracy: when &apos;done&apos; and the repository disagree</title>
      <link>https://laimonade.com/blog/why-done-and-the-repository-disagree</link>
      <guid isPermaLink="true">https://laimonade.com/blog/why-done-and-the-repository-disagree</guid>
      <pubDate>Sun, 20 Sep 2026 00:00:00 GMT</pubDate>
      <description>Status accuracy is a data-integrity problem wearing a discipline costume. A tracker holds no reference into the repository, and the error points one way.</description>
    </item>
    <item>
      <title>Agent work rejected: what to do when criteria are missed</title>
      <link>https://laimonade.com/blog/what-to-do-when-an-agent-returns-work-that-does-not-meet-criteria</link>
      <guid isPermaLink="true">https://laimonade.com/blog/what-to-do-when-an-agent-returns-work-that-does-not-meet-criteria</guid>
      <pubDate>Sat, 19 Sep 2026 00:00:00 GMT</pubDate>
      <description>A large share of agent work rejected at review is a specification defect, not a coding one. How to tell, and how to send it back so it fails differently.</description>
    </item>
    <item>
      <title>Do story points still work when agents do the building?</title>
      <link>https://laimonade.com/blog/do-story-points-still-work-with-coding-agents</link>
      <guid isPermaLink="true">https://laimonade.com/blog/do-story-points-still-work-with-coding-agents</guid>
      <pubDate>Fri, 18 Sep 2026 00:00:00 GMT</pubDate>
      <description>Story points still work, but they stop measuring effort and start measuring specification risk. Why the cheap-looking items are now the expensive ones.</description>
    </item>
    <item>
      <title>The agile standup when agents report their own work</title>
      <link>https://laimonade.com/blog/standups-and-status-when-agents-report-their-own-work</link>
      <guid isPermaLink="true">https://laimonade.com/blog/standups-and-status-when-agents-report-their-own-work</guid>
      <pubDate>Fri, 18 Sep 2026 00:00:00 GMT</pubDate>
      <description>The reporting half of an agile standup is redundant once the repository says what happened. What breaks is the coordination that was riding along with it.</description>
    </item>
    <item>
      <title>How many coding agents can one team actually run?</title>
      <link>https://laimonade.com/blog/how-many-coding-agents-can-one-team-run</link>
      <guid isPermaLink="true">https://laimonade.com/blog/how-many-coding-agents-can-one-team-run</guid>
      <pubDate>Thu, 17 Sep 2026 00:00:00 GMT</pubDate>
      <description>How many coding agents one team can run is set by two human queues rather than by compute, and most teams only ever count one of them.</description>
    </item>
    <item>
      <title>What changes about sprint planning with AI agents</title>
      <link>https://laimonade.com/blog/how-sprint-planning-changes-when-agents-do-the-building</link>
      <guid isPermaLink="true">https://laimonade.com/blog/how-sprint-planning-changes-when-agents-do-the-building</guid>
      <pubDate>Thu, 17 Sep 2026 00:00:00 GMT</pubDate>
      <description>Sprint planning with AI agents stops asking how much a team can take and starts asking how much of the work is genuinely ready to be executed.</description>
    </item>
    <item>
      <title>AI code review: reading what an agent actually did</title>
      <link>https://laimonade.com/blog/code-review-when-an-agent-wrote-the-code</link>
      <guid isPermaLink="true">https://laimonade.com/blog/code-review-when-an-agent-wrote-the-code</guid>
      <pubDate>Wed, 16 Sep 2026 00:00:00 GMT</pubDate>
      <description>In AI code review the summary is a claim and the diff is the evidence. Five things agents get wrong that people rarely do, and one no reviewer automates.</description>
    </item>
    <item>
      <title>How to write a coding agent work order it can act on</title>
      <link>https://laimonade.com/blog/how-to-give-a-coding-agent-a-work-order</link>
      <guid isPermaLink="true">https://laimonade.com/blog/how-to-give-a-coding-agent-a-work-order</guid>
      <pubDate>Wed, 16 Sep 2026 00:00:00 GMT</pubDate>
      <description>A coding agent work order has six parts, and a prompt has none of them. What to include, what to leave out, and what should come back when it is finished.</description>
    </item>
    <item>
      <title>Backlog dependencies in an agent-run sprint</title>
      <link>https://laimonade.com/blog/dependencies-and-sequencing-in-an-agent-backlog</link>
      <guid isPermaLink="true">https://laimonade.com/blog/dependencies-and-sequencing-in-an-agent-backlog</guid>
      <pubDate>Tue, 15 Sep 2026 00:00:00 GMT</pubDate>
      <description>Two sensible items that each need the other output cannot both be satisfied. Backlog dependencies fail quietly, as an unfinished checkbox.</description>
    </item>
    <item>
      <title>The coding agent workflow a team can actually run</title>
      <link>https://laimonade.com/blog/running-coding-agents-in-a-team-workflow</link>
      <guid isPermaLink="true">https://laimonade.com/blog/running-coding-agents-in-a-team-workflow</guid>
      <pubDate>Tue, 15 Sep 2026 00:00:00 GMT</pubDate>
      <description>A coding agent workflow is four stages: specify, dispatch, execute, verify. The stage teams skip is the first one, and the bill arrives at the fourth.</description>
    </item>
    <item>
      <title>The backlog audit to run before you point agents at it</title>
      <link>https://laimonade.com/blog/how-to-audit-a-backlog-before-pointing-agents-at-it</link>
      <guid isPermaLink="true">https://laimonade.com/blog/how-to-audit-a-backlog-before-pointing-agents-at-it</guid>
      <pubDate>Mon, 14 Sep 2026 00:00:00 GMT</pubDate>
      <description>A backlog audit is twenty items and four questions. Whatever you cannot answer from the item own text is the defect, and it is cheaper to find now.</description>
    </item>
    <item>
      <title>Splitting user stories small enough for a coding agent</title>
      <link>https://laimonade.com/blog/splitting-stories-for-coding-agents</link>
      <guid isPermaLink="true">https://laimonade.com/blog/splitting-stories-for-coding-agents</guid>
      <pubDate>Mon, 14 Sep 2026 00:00:00 GMT</pubDate>
      <description>One observable outcome per item, not one component per item. Why splitting user stories properly makes the estimate go up rather than down.</description>
    </item>
    <item>
      <title>Acceptance criteria an agent can verify, not just read</title>
      <link>https://laimonade.com/blog/acceptance-criteria-that-an-agent-can-verify</link>
      <guid isPermaLink="true">https://laimonade.com/blog/acceptance-criteria-that-an-agent-can-verify</guid>
      <pubDate>Sat, 12 Sep 2026 00:00:00 GMT</pubDate>
      <description>Acceptance criteria are verifiable when they name something you can run and an outcome you can observe. Five that fail that test, and their fixes.</description>
    </item>
    <item>
      <title>What a product owner costs a small engineering team</title>
      <link>https://laimonade.com/blog/what-product-ownership-costs-a-small-engineering-team</link>
      <guid isPermaLink="true">https://laimonade.com/blog/what-product-ownership-costs-a-small-engineering-team</guid>
      <pubDate>Sat, 12 Sep 2026 00:00:00 GMT</pubDate>
      <description>The product owner cost on a team of three to eight engineers is four to six hours a week, paid by whoever has least protection over their calendar.</description>
    </item>
    <item>
      <title>AI Product Owner vs human product owner</title>
      <link>https://laimonade.com/blog/ai-product-owner-vs-human-product-owner</link>
      <guid isPermaLink="true">https://laimonade.com/blog/ai-product-owner-vs-human-product-owner</guid>
      <pubDate>Fri, 11 Sep 2026 00:00:00 GMT</pubDate>
      <description>A human product owner decides what the product should become. An AI product owner turns those decisions into work an agent can execute, then checks it.</description>
    </item>
    <item>
      <title>Six signs your team has a product-ownership gap</title>
      <link>https://laimonade.com/blog/signs-your-team-has-a-product-ownership-gap</link>
      <guid isPermaLink="true">https://laimonade.com/blog/signs-your-team-has-a-product-ownership-gap</guid>
      <pubDate>Fri, 11 Sep 2026 00:00:00 GMT</pubDate>
      <description>Six symptoms of a product-ownership gap that read as ordinary team friction, and are one thing underneath: work is built faster than it is specified.</description>
    </item>
    <item>
      <title>Why coding-agent adoption stalls after the first month</title>
      <link>https://laimonade.com/blog/why-agent-adoption-stalls-after-the-first-month</link>
      <guid isPermaLink="true">https://laimonade.com/blog/why-agent-adoption-stalls-after-the-first-month</guid>
      <pubDate>Wed, 09 Sep 2026 00:00:00 GMT</pubDate>
      <description>Month one of coding-agent adoption spends a backlog written over the previous year. The stall that follows is a supply problem, not a model problem.</description>
    </item>
    <item>
      <title>What is MCP, and why does it matter for your backlog?</title>
      <link>https://laimonade.com/blog/what-is-mcp-and-why-it-matters-for-backlogs</link>
      <guid isPermaLink="true">https://laimonade.com/blog/what-is-mcp-and-why-it-matters-for-backlogs</guid>
      <pubDate>Fri, 04 Sep 2026 00:00:00 GMT</pubDate>
      <description>The Model Context Protocol turns a backlog from a page someone reads into a service an agent can call. What that changes, and what to withhold.</description>
    </item>
    <item>
      <title>Definition of done when an agent wrote the code</title>
      <link>https://laimonade.com/blog/definition-of-done-when-an-agent-wrote-the-code</link>
      <guid isPermaLink="true">https://laimonade.com/blog/definition-of-done-when-an-agent-wrote-the-code</guid>
      <pubDate>Tue, 01 Sep 2026 00:00:00 GMT</pubDate>
      <description>A commit message is a claim and the diff is the evidence. What a definition of done must say once the author is an agent, and why the last step is human.</description>
    </item>
    <item>
      <title>Who owns the backlog when agents write the code?</title>
      <link>https://laimonade.com/blog/who-owns-the-backlog-when-agents-write-the-code</link>
      <guid isPermaLink="true">https://laimonade.com/blog/who-owns-the-backlog-when-agents-write-the-code</guid>
      <pubDate>Wed, 26 Aug 2026 00:00:00 GMT</pubDate>
      <description>Backlog ownership splits into deciding what should exist and keeping each item executable. Only one of those two halves is still a meeting.</description>
    </item>
    <item>
      <title>How to write a backlog item an agent can execute</title>
      <link>https://laimonade.com/blog/how-to-write-a-backlog-item-an-agent-can-execute</link>
      <guid isPermaLink="true">https://laimonade.com/blog/how-to-write-a-backlog-item-an-agent-can-execute</guid>
      <pubDate>Wed, 19 Aug 2026 00:00:00 GMT</pubDate>
      <description>A backlog item for AI agents needs five fields a human reader never asks for. Here they are, with one real item rewritten from unusable to executable.</description>
    </item>
    <item>
      <title>What an AI Product Owner actually does</title>
      <link>https://laimonade.com/blog/what-an-ai-product-owner-actually-does</link>
      <guid isPermaLink="true">https://laimonade.com/blog/what-an-ai-product-owner-actually-does</guid>
      <pubDate>Wed, 12 Aug 2026 00:00:00 GMT</pubDate>
      <description>An AI product owner turns decisions into work an agent can execute, sequences it, hands it over, and checks what comes back. Deciding stays human.</description>
    </item>
    <item>
      <title>A backlog an agent can actually read</title>
      <link>https://laimonade.com/blog/a-backlog-an-agent-can-read</link>
      <guid isPermaLink="true">https://laimonade.com/blog/a-backlog-an-agent-can-read</guid>
      <pubDate>Wed, 05 Aug 2026 00:00:00 GMT</pubDate>
      <description>Four backlog failure modes that stand between a normal backlog and an agent-ready backlog. Each reads as an ordinary unfinished ticket.</description>
    </item>
  </channel>
</rss>
