← ClaudeAtlas

atom-operating-modellisted

Default operating model for non-trivial work: act as a coordinating PM that fans out a team of isolated, communicating worker agents, with parallel work in separate git worktrees. Trigger on "arbeite im Team", "parallel bearbeiten", "koordiniere Agenten", "mehrere Tasks gleichzeitig", "spawn a team", "fan out", "work on these in parallel", "PM mode", "split this across agents". Defines worktree topology rules, the main-thread-PM mesh, peer-to-peer comms governance, and an execution-context boundary (full background mesh only in interactive sessions; headless/spawned agents use the synchronous subset only). NOT for trivial single-step tasks — those stay with the coordinator. For single-feature delivery detail use the project's OFD harness; this is the layer above that distributes streams.
lx-wnk/skills · ★ 1 · AI & Automation · score 71
Install: claude install-skill lx-wnk/skills
# Agent-Team Operating Model (ATOM) Structured PM coordination for non-trivial parallel work: one coordinating main-thread PM, multiple isolated worker agents, each in its own git worktree. ## Scope **DOES:** - Act as PM: decide topology, create worktrees off `main`, fan out workers, govern peer comms, own merge and conflict resolution - Choose the correct worktree topology based on task structure (see Topology rules below) - Dispatch parallel worker streams via background `Agent` calls (main thread only) - Govern peer-to-peer communication between workers (contracts-first, budget-bounded) - Integrate results per the topology rule; verify via `git log` and CI **Does NOT:** - Handle trivial single-step tasks (≤1 tool call) — those stay with the coordinator directly - Replace OFD: a single worker stream is itself an OFD run; ATOM is the layer above that distributes streams - Implement the dashboard's native PM-agent feature (Plane B) — this skill governs interactive sessions only ## When it triggers The global rule is the trigger: **delegate when >1 tool call; the coordinator stays a lean PM.** Any time work decomposes into multiple independently executable streams — code, docs, analysis, or mixed — load this skill and choose a topology before dispatching. ## Examples ```bash # Three independent tasks dispatched in parallel, each gets its own PR /atom-operating-model "implement A, B, C (independent)" ``` ```bash # One feature split file-disjointly across two agents,