القائمة
Agent team orchestration conventions for persistent multi-agent coordination via shared task lists and messaging.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Index curated reference corpora into a searchable knowledge graph via the cognee engine, then query it to ground technical writing, review, and analysis. Use when ingesting reference documents into named datasets or retrieving grounding context for tasks like drafting or reviewing a manuscript. A reference-knowledge index, explicitly not agent session memory.
Nix development conventions for flakes, derivations, modules, and code style. Use when authoring flake.nix files, writing derivations or builders, designing NixOS/nix-darwin/home-manager modules, or following nix formatting and naming conventions. For check architecture and CI integration, see preferences-nix-checks-architecture and preferences-nix-ci-cd-integration.
Approximately-verifiable, refinement-driven development for type-driven domain-driven design. Use when modeling a domain as a dependently-typed Lean 4 specification, refining/lowering it to a Rust implementation, lifting the implementation back via Charon and Aeneas to check spec<->implementation correspondence (translation validation) — mechanically when tractable, otherwise via differential testing or LLM comparison — or when generating and diffing type-system diagrams of the model and implementation to track their evolution. Mechanical on-the-nose proof is the precise ideal, not a requirement; its absence is not a failure of the method.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Algebraic data type patterns including sum types, product types, and pattern matching across languages. Load when designing type hierarchies or working with discriminated unions.
Algebraic laws including functor/monad laws and property-based testing strategies. Load when verifying algebraic properties or writing property tests.
| name | meta-agent-teams |
| description | Agent team orchestration conventions for persistent multi-agent coordination via shared task lists and messaging. |
Agent teams are a second orchestration mode alongside DAG dispatch of subagent Tasks. Use this reference when spawning or coordinating persistent agent teams.
Teammates do not inherit the orchestrator's conversation context, so spawn prompts must be self-contained with all necessary context, file paths, and objectives. Teammates coordinate via shared task list (TaskCreate/TaskUpdate/TaskList) and messaging (SendMessage), not by returning results to the orchestrator. The orchestrator remains responsible for teammate lifecycle management.
Beads-to-task-list mirroring aligns ephemeral team coordination with persistent issue tracking. When an agent team works on an epic lineage or cross-cutting collection of beads issues, mirror the relevant issues and their dependencies into the team's shared task list via TaskCreate with appropriate blockedBy/blocks relationships. The team's shared task list is the ephemeral coordination substrate; beads issues remain the persistent source of truth. Keep both in sync: when a team task completes, update the corresponding bead.
Teammate lifecycle management integrates with the orient/checkpoint pattern.
Every new teammate should be instructed to execute /session-orient at session start to establish full context on the issue graph and current state.
For repos without the full workflow (no session-* skills installed), fall back to /issues-beads-orient.
Teammates should monitor context usage and, when approaching 50% capacity (approximately 100k tokens), execute /session-checkpoint to capture learnings, update issue status, and produce a handoff narrative.
For repos without the full workflow, fall back to /issues-beads-checkpoint.
After checkpoint, the teammate requests shutdown; the orchestrator spawns a replacement oriented with /session-orient (or /issues-beads-orient in beads-only repos) to continue the work.
This creates a clean lifecycle: orient, work, checkpoint, shutdown, replace.
The "You are a subagent Task" identity marker and return-with-questions pattern apply to DAG-dispatched tasks. For agent team teammates, spawn prompts should include equivalent identity context plus instructions about the orient/checkpoint lifecycle.
Teammates spawned in agent teams cannot edit files directly. The harness gates direct Edit, Write, and MultiEdit calls for teammate-class agents, surfacing this as an EnterWorktree prompt that should never be satisfied by creating a worktree in jj-mode workspaces. Instead, teammates dispatch a subagent Task for every file edit. The subagent inherits the teammate's working directory and operates against the same jj working copy, so no worktree is needed and no parallel-filesystem state arises.
Dispatched subagent Task input MUST NOT set isolation: "worktree".
In jj-mode repositories this parameter is hook-blocked at the Agent tool surface, but teammates should omit it unconditionally to keep behavior consistent across modes.
The subagent edits at @ (which in tier 3 is the wip commit atop the development join, per ~/.claude/skills/jj-version-control/SKILL.md's composite maintenance invariant), and the orchestrator routes the resulting changes to the appropriate chain via the route-and-extend recipe (jj new -A <chain-tip> --no-edit -m "..." then jj squash --from @ --into <new-change-id> --keep-emptied then jj bookmark move <name> --to <new-change-id>).
All teammates edit that same @=[wip], which is the shared coordination surface that makes N concurrent editors safe by construction; routing the diff downward with --keep-emptied is load-bearing because it leaves @ an empty [wip] in place for the others still writing it.
Never jj describe @ into content and never relocate @ below the join via positional jj rebase -r @ --insert-before/--insert-after (nor the --revisions @ form); both drift the shared surface off [wip].
Full canon — including the sanctioned destination-form jj rebase -r @ -d 'all:(…)' and the complete editor-safe routing-down templates — lives in ~/.claude/skills/jj-version-control/SKILL.md invariant (iii-b)/(vi).
This is the agent-team specialization of the binding orchestrator-dispatch discipline documented in ~/.claude/CLAUDE.md.
The same pattern applies to any orchestrator subject to a harness-level edit-gate (background sessions, future isolation requirements); teammates are simply the most common case in team-coordinated work.
The implicit assumption that @ is stable for the dispatch lifetime breaks during master-orchestrated restructures; see meta-orchestrator-initiate/01-discipline-and-cycle-patterns.md §"Subagent-@-inheritance race during restructure" for the pre-restructure quiescence, post-restructure inspection, and routed re-entry disciplines that preserve diamond shape under that race.
