coordinate-multihost-work

Coordinate Linux, Windows, and macOS implementation agents through shared plan ledgers and git branch audits.

5|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/8007342/tillandsias --skill coordinate-multihost-work-8007342
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: coordinate-multihost-work
Source: https://github.com/8007342/tillandsias/tree/main/skills/coordinate-multihost-work
Command: npx skills add https://github.com/8007342/tillandsias --skill coordinate-multihost-work-8007342

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Distributed implementation agents working on separate platform branches (linux-next, windows-next, osx-next) drift apart, deadlock on each other, thrash shared files, and lose track of claimed work. This Skill runs an hourly coordination pass that keeps all hosts unblocked and guarantees finite-time convergence on the specs. ## Core Features & Use Cases - Cross-Branch Claim Auditing: Folds sibling branch state before routing work, so a packet claimed on osx-next is never mistaken for unclaimed on trunk. - Deadlock and Thrashing Mediation: Detects mutual waiting, spec divergence, write-write collisions, and branch drift, then freezes leases and assigns corrective tasks. - Convergence Velocity Enforcement: Computes residual correctness debt and convergence velocity, triggering high-velocity alignment events with reduced lease TTLs when progress stalls. - Integration and Litmus Execution: Merges sibling branches into linux-next, runs the litmus suite on the merged union, and pushes coordination updates. - Use Case: A coordinator agent runs this skill hourly to reconcile plan.yaml ledgers, assign each host a primary and fallback packet, and verify that merged platform branches pass the runtime litmus before push. ## Quick Start Run an hourly coordination pass that audits the sibling platform branches, reconciles the shared plan ledgers, assigns unblocked work to each host, and pushes the updates to origin/linux-next.

Frequently Asked Questions about coordinate-multihost-work

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

FAQPage Schema
How do I coordinate multiple AI agents working on separate git branches?▼

Run an hourly coordination pass that fetches all sibling branches, folds their claim state before routing work, and assigns each host a primary plus fallback packet. Push all coordination updates to a shared trunk branch like linux-next before ending the loop.

How to detect when a task is claimed on another branch?▼

Run a cross-branch claim check script against every candidate packet before routing it. A trunk-only read misses claims pushed to sibling branches like osx-next, since relay delays can hide them for hours.

What causes branch drift in multi-host development workflows?▼

Branch drift happens when a sibling branch accumulates commits not integrated into the trunk branch. Measure it with git rev-list --count and trigger an alert when the count exceeds five commits, then force a merge-based integration task.

How do I prevent agents from thrashing shared files?▼

Detect thrashing by watching for repeated overwrites in git history, then freeze both active leases and enforce semantic upserts keyed by stable IDs. Assign conflict resolution to one host while the other works an independent fallback path.

When should lease TTLs be reduced in distributed agent coordination?▼

Reduce lease TTL from four hours to one hour when convergence velocity falls below one correctness unit per hour while residual debt remains. This forces faster heartbeats and handoffs during a high-velocity alignment event.