{"product_id":"surface-charter-non-overlapping-write-territory-generator-for-multi-agent-claude-code-teams","title":"Surface Charter — Non-Overlapping Write-Territory Generator for Multi-Agent Claude Code Teams","description":"\u003cp\u003e\u003cstrong\u003eInspired by cbrock84\/headcount, an \"AI agents as a company org chart\" project trending on GitHub this week (1.5k+ stars) for one idea in particular: splitting agent work by exclusive write surface instead of topic, so parallel agents never fight over the same file.\u003c\/strong\u003e Headcount ships that idea as a fixed 16-department company template. Surface Charter does the opposite — it's a generator that builds the territory map for your actual agents, whether that's two subagents or a five-person agency's worth.\u003c\/p\u003e\n\n\u003ch3\u003eWhat this Claude Skill does\u003c\/h3\u003e\n\u003cul\u003e\n  \u003cli\u003eInterviews Claude about your real subagents\/skills — names, roles, the paths each one touches — and drafts a territory map sized to your team, not a generic org chart\u003c\/li\u003e\n  \u003cli\u003eAssigns every writable path to exactly one owner, with an optional non-owning reviewer role that gets blocking authority without claiming any files itself\u003c\/li\u003e\n  \u003cli\u003eShips a working, tested Python validator that catches overlapping globs between agents — including nested-directory and root-level wildcard cases a naive string-prefix check gets wrong — and exits non-zero for CI\u003c\/li\u003e\n  \u003cli\u003eIncludes three ready-to-adapt starting shapes (solo builder, two-person team, small agency with parallel client workstreams) plus a deliberately broken example so you can see a caught conflict before you need one\u003c\/li\u003e\n  \u003cli\u003eHands back both a human-readable SURFACE-MAP.md and a machine-checkable surface-map.yaml, with a one-line suggestion for wiring the validator into your CI\u003c\/li\u003e\n\u003c\/ul\u003e\n\n\u003ch3\u003eBuilt for\u003c\/h3\u003e\n\u003cul\u003e\n  \u003cli\u003eAnyone running 2+ persistent Claude Code subagents on one repo who has already had two agents clobber the same file\u003c\/li\u003e\n  \u003cli\u003eTeams scaling from one agent to several who want the ownership boundary decided up front instead of discovered in a merge conflict\u003c\/li\u003e\n  \u003cli\u003eAgencies running parallel client workstreams in one monorepo who need workstreams that structurally cannot bleed into each other\u003c\/li\u003e\n\u003c\/ul\u003e\n\n\u003ch3\u003eWhat's inside\u003c\/h3\u003e\n\u003cul\u003e\n  \u003cli\u003e\n\u003cstrong\u003eSKILL.md\u003c\/strong\u003e — the full skill file: when to use it, the four-step method (inventory, draft, validate, hand back), and the rules for assigning territory without over-scoping\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003escripts\/validate_surfaces.py\u003c\/strong\u003e — a standard-library conflict checker (PyYAML optional, JSON works with zero dependencies) that generates concrete candidate paths from each glob and cross-tests them, catching overlaps that plain prefix-matching misses\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003etemplates\/solo-builder.yaml, two-person-team.yaml, agency.yaml\u003c\/strong\u003e — starting territory maps for three common team shapes\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eexamples\/conflict-example.yaml\u003c\/strong\u003e — a deliberately broken map that reproduces two real collision patterns (nested directory overlap, root-level wildcard overlap) so you can see the validator's output before you need it\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eREADME.md \u0026amp; LICENSE\u003c\/strong\u003e — install instructions, standalone CLI usage, a CI snippet, and usage terms\u003c\/li\u003e\n\u003c\/ul\u003e\n\n\u003ch3\u003eHow a Claude Skill works\u003c\/h3\u003e\n\u003cp\u003eThis is a \u003ca href=\"https:\/\/platform.claude.com\/docs\/en\/agents-and-tools\/agent-skills\/overview\" rel=\"nofollow\"\u003eClaude Skill\u003c\/a\u003e — a single SKILL.md file Claude reads as instructions for a specific kind of work. Drop it in your Claude Project, .claude\/skills\/ folder, or wherever Claude can read it. Claude triggers the skill automatically when your prompt matches its description — setting up subagents, or reporting that two agents keep overwriting each other — then runs the four-step method end to end.\u003c\/p\u003e\n\n\u003ch3\u003eAuthor\u003c\/h3\u003e\n\u003cp\u003eBuilt by \u003cstrong\u003eUkiyo Productions\u003c\/strong\u003e — a strategy-led branding and growth agency. Part of a 100+ skill marketplace built for founders, operators, consultants, and agencies.\u003c\/p\u003e","brand":"Ukiyo Productions","offers":[{"title":"Default Title","offer_id":47682166653012,"sku":"UKIYO-SURFACECHARTER","price":29.0,"currency_code":"USD","in_stock":true}],"url":"https:\/\/ukiyoprod.com\/products\/surface-charter-non-overlapping-write-territory-generator-for-multi-agent-claude-code-teams","provider":"Ukiyo","version":"1.0","type":"link"}