This is a placeholder. The written case study has not been handed off yet.
The finished version arrives from the Drive handoff as
Clembot/site-anatomy-parallel-subagent-game-dev.md and is ingested by
node scripts/site-anatomy-pull.js, which overwrites this file body while
keeping the frontmatter contract. It is not written by hand and the site build
never reaches Drive.
What it will cover, from the settled outline:
- How work gets split so that several agents can run against one repository without fighting over the same files.
- Which steps genuinely parallelise (independent features, independent assets) and which are stubbornly sequential (schema, shared state, the final build).
- The failure modes: duplicated work, contradictory edits, and the review load that fan-out creates downstream.
Live output of this pattern: games.wanessalabs.com.