parallel-worktree-delivery
Skill0 starsChanged 4 months agoMITView on GitHub
Executes multi-agent Git worktree fleets with exclusive ownership, dependency waves, serialized integration, and merge gates. Use when delivering independent streams on separate branches/worktrees; not for task planning alone, one small change, or GitHub-hosted cloud agents.
In this repository24 other files it gives its agents.
- AGENTS.mdAGENTS.md
- agent-tool-interface-designSkill
- codebase-explorationSkill
- code-reviewSkill
- copilot-cloud-agentSkill
- documentation-maintenanceSkill
- external-skill-reviewSkill
- git-and-pr-workflowSkill
- planning-and-task-breakdownSkill
- refactoring-and-dead-code-removalSkill
- repository-agent-bootstrapSkill
- requirements-and-spec-writingSkill
- security-reviewSkill
- shadow-architectureSkill
- shadow-dreamSkill
- shadow-driftSkill
- shadow-observeSkill
- skill-creatorSkill
- systematic-debuggingSkill
- test-driven-developmentSkill
- verification-before-completionSkill
- verification-disciplineSkill
- wayfinder-planningSkill
- web-research-and-verificationSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
Run only an authorized fleet.
- Very specific: line 18
Read path instructions; inspect branch/status/worktrees/operations and verify base/integration checkout.
- Distinctive: line 25
Before delegation, complete the capability preflight in fleet setup: resolve required skills to supported native names or authorized source …
- Distinctive: line 56
Read integration playbook before merges.
- Distinctive: line 61
Run all repository-required per-merge gates after each merge.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Parallel Worktree Delivery
Run only an authorized fleet; loading is not consent to spawn, install, or mutate Git/remote state.
Prepare
- Read path instructions; inspect branch/status/worktrees/operations and verify base/integration checkout. Never stash, commit, switch, or overwrite others' live work.
- Bound streams/concurrency/time/cost to approved resources. Delegate substantial independent work only; honor requested runtime/model, invent no controls.
- Assign separate branches/worktrees and exclusive files; sequence dependencies in waves. Coordinator owns shared files; exact-section exceptions serialize writes.
- Before delegation, complete the capability preflight in fleet setup: resolve required skills to supported native names or authorized source paths and record actual messaging limits. Carry verified routes into worker prompts; block unsupported dependent work instead of installing globally or expanding permissions. Isolate or serialize writable dependencies, caches, outputs, databases, and ports. No concurrent shared installs; bound CPU-heavy jobs.
Dispatch and collect
- Supply objective/stop, branch/worktree/base, ownership, instructions/setup, scoped checks, allowed actions, and the capability contract. Workers confirm loading routes before dependent work and report cross-boundary needs, not edit.
- Record runtime/provider, requested and observed model (or unknown), usable worker handle, and owned repository/worktree/branch/base/tip in the handoff. Continue independent work. Use notifications/bounded known-ID waits, not tight polling/discovery or duplicate workers. Collect paths/commits, exact checks/results, conflicts, and boundary requests.
- Session/task IDs from history are not necessarily addressable worker IDs. Confirm the runtime's visible handle and message capability before contacting an external or resumed worker. On an unavailable handle, preserve its checkout ownership and use a durable handoff or report blocked; do not repeatedly send, spawn a replacement owner, or infer that its files are free to edit.
- Send only to explicit known message-capable handles. Deduplicate recipients and batch within the host-reported limit; do not hardcode a provider cap or use broad scopes to bypass it. One-shot workers are result-only unless the host explicitly supports follow-up. Unknown capabilities are blockers, not permission to probe by sending.
Integrate
- Read integration playbook before merges. Freeze tips; review ownership/full diffs. Serialize integration/shared Git administration in the clean coordinator checkout.
- Merge one stream at a time; reconcile both conflict intents. Stop on unresolved ownership/behavior disagreements or failed checks.
- Run all repository-required per-merge gates after each merge. Without a mandated full gate, check integrated changes/interactions. Never substitute worker/pre-merge evidence or defer required gates to the final wave.
- Coordinator owns integration fixes; rerun affected checks/required gates before another merge without resource races. Review final diff/required final gates; no unchanged scoped reruns solely for handoff. Stage explicit owned paths; remote writes/clean-worktree cleanup need consent.
Output
Return waves/ownership, worker IDs/integrated tips, per-merge checks/results, conflicts/fixes, and pending work/blockers. No transcript dump; distinguish local integration from remote delivery.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

