agent-teams-command

# Agent Teams Command <skill_contract> <input>A mission with independently ownable workstreams, interfaces, permissions, budgets, and an integration owner.</input> <output>An isolated worker program, typed IPC ledger, serial integration, cleanup, and evidence receipts.</output> <done>Integrated artifacts pass mission checks and ownership, review, rollback, and cleanup gates.</done> <non_goals>Graph-schema design, parallelism without net value, overlapping writers, or worker self-certification.</non_goals> Strategic intent and final integration remain serial; owned execution may run in parallel. `graph-engineering` may define dependency topology, but this skill owns worker processes, exclusive territories, typed IPC, integration, and cleanup. A Graph node is not automatically a teammate. Use the Ender lens for commander understanding, Palantir for operational objects/actions, and von Neumann for executable, inspectable process architecture. Detailed patterns: `references/ender-palantir-command-patterns.md`; examples: `references/classic-campaigns.md`. ## Usage Template Provide: mission, non-goals, workstreams, dependencies, files/systems, acceptance criteria, permissions, review bandwidth, runtime capabilities, budget, and integration owner. ## Workflow <intake> Admit a team only when at least two workstreams can proceed with low coordination, or distinct roles materially improve evaluation/safety. Calculate orchestration tax: setup, context duplication, IPC, me...