跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
开发与测试

git-worktree-swarm

Automates the complex setup of parallel git worktrees for agentic swarms with dependency-aware wave execution.

winstonkoh87 · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add winstonkoh87/Athena-Public --skill git-worktree-swarm

技能说明


name: git-worktree-swarm description: Automates the complex setup of parallel git worktrees for agentic swarms with dependency-aware wave execution. argument-hint: "deploy | cleanup | waves" allowed-tools:

  • Bash auto-invoke: false model: default context_trigger: "worktree, parallel agents, swarm, multi-agent, concurrent development, wave execution"

Git Worktree Swarm Orchestrator

Sets up parallel, isolated git environments so multiple sub-agents can work on the same repository simultaneously without merge conflicts. Uses wave-based execution to respect task dependencies.

Triggers

"swarm", "parallel agents", "setup worktrees", "multi-agent", "wave execution"

Core Mechanics

Phase 1: Setup

  1. Detect current branch.
  2. Spawn n temporary worktrees (.agent-workspace-1, etc.).
  3. Assign tasks to isolated clones.

Phase 2: Wave Execution (Dependency DAG)

Plans are grouped into waves based on dependency analysis:

WAVE 1 (parallel — no dependencies)
├── Worktree A: Task 1 (User model)     → Fresh context (P513)
├── Worktree B: Task 2 (Product model)  → Fresh context (P513)
│
[State merge: A.state + B.state → combined handoff]
│
WAVE 2 (parallel — depends on Wave 1)
├── Worktree C: Task 3 (Orders API, needs User model)
├── Worktree D: Task 4 (Cart API, needs Product model)
│
[State merge: C.state + D.state → combined handoff]
│
WAVE 3 (sequential — depends on Wave 2)
└── Worktree E: Task 5 (Checkout UI, needs Orders + Cart)

Wave Assignment Rules:

ConditionAssignment
Task has no dependenciesWave 1
Task depends on Wave N outputWave N+1
Tasks touch the same filesSame wave, sequential (not parallel)
Task has cross-cutting concernsLatest wave of any dependency

Phase 3: Context Isolation (P513)

Each worktree agent receives only:

  • The specific plan/task
  • Relevant source files (from dependency analysis)
  • STATE.md (accumulated decisions from prior waves)
  • Project context (design.md / REQUIREMENTS.md)

Never: full conversation history, debug logs, unrelated research.

Phase 4: Merge

  1. Each task commits atomically (P43 micro-commit).
  2. Merge worktrees back to main branch in wave order.
  3. Conflict resolution: if merge conflicts arise, spawn resolution agent.
  4. Cleanup: remove temporary worktrees.

Reference Paths

  • Protocol 513: Context Isolation
  • Protocol 43: Micro-Commit
  • .context/memories/protocols/engineering/100-git-worktree-parallelism.md
  • .context/memories/protocols/architecture/409-parallel-worktree-orchestration.md