skills.rest
Yoodaddy0311
Yoodaddy0311COMMUNITY
Explore all skills by this author →
GitHub

split

Coordinates parallel Claude Code windows across git worktrees with non-overlapping file ownership.

3|2|Updated Feb 13, 2026
Search Tags:#claude code#orchestration#git worktree#cross-session#parallel sessions#multi-window#branch coordination
One-click install
npx skills add https://github.com/Yoodaddy0311/artibot --skill split-yoodaddy0311
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: split
Source: https://github.com/Yoodaddy0311/artibot/tree/main/plugins/artibot/skills/split
Command: npx skills add https://github.com/Yoodaddy0311/artibot --skill split-yoodaddy0311

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Large tasks bottleneck on a single session's context, leader, and landing pipeline. This Skill splits work across multiple Claude Code windows, each running in its own git worktree with disjoint file ownership, so stems progress in parallel without colliding. ## Core Features & Use Cases - Multi-window fan-out: Plans stems with /split plan, opens one window per stem via claude --worktree, and tracks completion through Split-Limb: done git commit trailers rather than messages. - Operations scripts: dispatch renders briefs and pointer messages, land runs a 7-row landing check (trailer, ownership, binary, citations, merge dry-run, lint), watch and probe observe lane health, and worktree-setup wires node_modules junctions and per-lane env files. - Safety guardrails: Humans open and close windows; scripts never send messages, push, or merge. Cross-session messages are treated as data, not instructions. - Use Case: A multi-day PRD is split into three stems with disjoint file ownership; each window works its own worktree, and the parent window verifies completion via commit trailers and merge-tree conflict checks before recombination. ## Quick Start Ask the assistant to split this task across multiple worktree windows using the split skill, starting with a stem plan.

Frequently Asked Questions about split

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run parallel Claude Code sessions on one repository?▼

Use the split workflow: run `/split plan <task>` to create a stem plan, then manually open a new terminal per stem with `claude --worktree split-<repo>-<limb>` from the repo root. Paste each stem's brief and start prompt into its window as the first message.

How does multi-worktree split track completion across sessions?▼

Completion is detected from git commit trailers, not messages. Each window finishes by leaving a `Split-Limb: done` trailer on its last commit, and the parent window verifies with `/split status`, since trailers survive session death and message loss.

When should I use split instead of a single-window agent team?▼

Use split only when work spans two or more stems with disjoint file ownership and one leader is the bottleneck. Stay with a single-window team for single dependency chains, tasks touching one shared file or dev-server port, or when you cannot open a second terminal.

Does the split skill create git worktrees automatically?▼

No. Humans open and close windows; the plugin never runs `git worktree add` or spawns headless sessions, because choosing permission postures for unseen sessions would be permission laundering. Scripts only measure and report; leaders send messages, push, and merge.

Why does the landing check fail on Korean file paths?▼

Git's default `core.quotepath` setting C-quotes non-ASCII paths, which the ownership parser reads as allowlist violations. The land script uses `git diff --name-only -z` with NUL-separated output to avoid this false FAIL.

What are the limits of cross-session coordination with split?▼

The window cap is 8 with a hard worktree cap of 12. `ListAgents` output lacks working directories, so it is only a name-prefix heuristic; the truth source is `git worktree list --porcelain`. A PASS from the land script is not approval—human review still decides.

Related Skills

Explore More Software Engineering Skills→
ConsiliencyConsiliency
2

claude-plan-phase

Generates interface-freeze phase plans with parallel swim lanes from versioned roadmaps.

Official
Advanced
DenissvgnDenissvgn

merge-agent

Automate authorized feature branch merges into main with validation and rollback.

Community
Basic
AesopScottAesopScott

stall-tuner

Calibrate heartbeat intervals and stall thresholds in the Health Monitor harness.

Community
Intermediate
malhashemimalhashemi
20

parallel-research

Decompose large research questions into parallel sub-tasks and synthesize findings into a Markdown report.

Community
Advanced