<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>AgentCrew engineering blog</title><description>Notes on running coding agents like an engineering team.</description><link>https://agentcrew.to/</link><language>en</language><item><title>“Done” is a claim until there is evidence</title><link>https://agentcrew.to/blog/done-is-a-claim-until-there-is-evidence/</link><guid isPermaLink="true">https://agentcrew.to/blog/done-is-a-claim-until-there-is-evidence/</guid><description>Why an agent&apos;s completion message is the least reliable artefact in your pipeline, and how evidence-gated completion tied to commits and requirements fixes it.</description><pubDate>Thu, 17 Sep 2026 00:00:00 GMT</pubDate><category>verification</category><category>agents</category><category>process</category><author>Harish Ganapathi</author></item><item><title>One worktree per task: parallel agents without collisions</title><link>https://agentcrew.to/blog/a-worktree-per-task/</link><guid isPermaLink="true">https://agentcrew.to/blog/a-worktree-per-task/</guid><description>How isolating every agent task in its own Git worktree makes parallel coding agents safe, why integration should be an explicit merge, and why conflicts must block.</description><pubDate>Tue, 15 Sep 2026 00:00:00 GMT</pubDate><category>git</category><category>parallelism</category><category>agents</category><author>Harish Ganapathi</author></item><item><title>A prompt is not a specification</title><link>https://agentcrew.to/blog/a-prompt-is-not-a-specification/</link><guid isPermaLink="true">https://agentcrew.to/blog/a-prompt-is-not-a-specification/</guid><description>Coding agents build the wrong thing at full speed unless requirements come first. How stable IDs, acceptance criteria and revisions make plans agents can be held to.</description><pubDate>Sat, 12 Sep 2026 00:00:00 GMT</pubDate><category>specs</category><category>planning</category><category>process</category><author>Harish Ganapathi</author></item><item><title>Two approvals, not zero: humans in an agent pipeline</title><link>https://agentcrew.to/blog/two-approvals-not-zero/</link><guid isPermaLink="true">https://agentcrew.to/blog/two-approvals-not-zero/</guid><description>Full autonomy is a demo and babysitting is a chore. The right number of human interruptions in an engineering change is two: approve the plan, approve delivery.</description><pubDate>Tue, 08 Sep 2026 00:00:00 GMT</pubDate><category>autonomy</category><category>process</category><category>agents</category><author>Harish Ganapathi</author></item></channel></rss>