What problem does it solve? When multiple agents work on the same repository artifacts at the same time, they can overwrite each other's outputs, corrupt shared state, or make conflicting decisions. This Skill prevents that by enforcing deterministic concurrency control with leases, fencing tokens, and explicit ownership rules. ## Core Features & Use Cases - Lease-Based Ownership: Issues and renews leases with fencing tokens, TTLs, and explicit read/write scopes so only one agent holds exclusive write access at a time. - Conflict Detection and Resolution: Rejects conflicting claims deterministically, records conflict outcomes and retries, and provides resume guidance for expired leases. - Ownership Transfer: Coordinates safe handoffs by requiring the current owner to release before the next owner accepts. - Use Case: Two agents both need to update the same workflow report. The coordinator grants an exclusive-write lease to one, rejects the other's claim with a deterministic conflict reason, and publishes the coordination state to reports/coordination-state.json for downstream observability. ## Quick Start Ask the agent to coordinate two concurrent agents contending for the same report output using exclusive-write lease semantics.
