<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Subagents on philliant</title><link>https://philliant.com/tags/subagents/</link><description>Recent content in Subagents on philliant</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 philip mathew hern</copyright><lastBuildDate>Mon, 10 Aug 2026 03:00:00 -0700</lastBuildDate><atom:link href="https://philliant.com/tags/subagents/index.xml" rel="self" type="application/rss+xml"/><item><title>one agent, one repo, one writer at a time</title><link>https://philliant.com/posts/20260810-one-agent-one-repo-for-writes/</link><pubDate>Mon, 10 Aug 2026 03:00:00 -0700</pubDate><guid>https://philliant.com/posts/20260810-one-agent-one-repo-for-writes/</guid><description>parallel agents can review different folders at once, but only one agent should write to a repo at a time. other agents keep scanning the tree for context while files change under them, and that moving ground produces confused plans, stale assumptions, and merge collisions you did not expect.</description></item><item><title>parallel subagents: when to use them vs regular skills</title><link>https://philliant.com/posts/20260808-parallel-subagents-when-to-use-them-vs-skills/</link><pubDate>Sat, 08 Aug 2026 05:39:48 -0700</pubDate><guid>https://philliant.com/posts/20260808-parallel-subagents-when-to-use-them-vs-skills/</guid><description>skills are the right tool for one bounded workflow. parallel subagents are the right tool when the same workflow must run across several independent units at once. the parent dispatches, aggregates, and keeps shared writes serial.</description></item></channel></rss>