who is holding this file right now
agent-sync
Coordination plane for concurrent agents: leases with a TTL so two agents cannot claim the same work, race-free id reservation, a run journal and a generated board, over a pluggable knowledge cloud.
What it ships
Each name below is an entry point an agent can be routed to.
- agent-sync
Shape: static. Leases, ids and the journal are a fixed protocol; what varies is who holds what, which is state rather than shape.
Install just this one
Every pack installs standalone. The whole family is one command.
npx skills add ssheleg/agent-sync
claude plugin marketplace add ssheleg/agent-sync && claude plugin install agent-sync@agent-sync
When the agent reaches for it
These are the rules the family writes into your agent's own instruction file — verbatim. Each one states the rule, the boundary in both directions, and the phrase that declines it.
/agent-sync — who is holding this file
- when: the project has agent coordination on
- decline it: «без координации».
If agent-sync is installed AND the project has .claude/agent-sync.json, shared registries are edited only under a claim — decisions, open questions, roadmap, workstreams, dependencies. The claim is taken BEFORE the edit, ids are reserved race-free, the run is journalled. This holds even when nobody asked about coordination: an unclaimed edit to a shared file is how two agents overwrite each other.
The boundary — "a file in a project where coordination is on." NOT through it: a project with no .claude/agent-sync.json, ordinary code files, working alone. Taking a lease to edit a README in a repository where you are the only agent is how you teach an agent to route around it.
Refusal phrase: «без координации».
Among the routers: task-pipeline decides how a change reaches the repository; agent-sync who is holding this file right now. The second matters only where there is more than one agent.
The rest of the family
super-ux v0.48.0
Scenario-driven UI development: a versioned design chain in docs/ux/ — the product vision, personas and jobs, user flows and the paid-acquisition funnel among them, a screens-and-states map with Figma frames…
task-pipeline v1.77.0
Full-cycle delivery orchestrator: an intake grill turns the request into a complete brief, then ten gated stages carry it from docs to acceptance, refusing to advance until each gate passes.
make-skill v0.23.1
A skill that builds skills: create, retrofit, audit and publish agent skills and Claude Code plugins — Agent Skills standard conformance, marketplace layout, version sync, validator + CI, every distribution…
sheleg-design v1.49.1
The taste layer: cinematic scroll-driven landing pages (one scroll clock, motion that degrades to calm, WebGL particle formations), product-UI style packs with a ready token layer each, and the Figma border…
seo-aeo-audit v0.25.1
Evidence-first website audit for search and answer engines: ten tracks from crawl access to AI citation mechanics, every finding backed by an observation and every recommendation tiered, ending in a…
sheleg-dev v0.10.0
The integration layer a product reaches once it has users: Stripe subscription billing reconciled into your own database — checkout, renewals, seats and proration, refunds, claim-first webhook idempotency…
agent-stack v0.13.2
Production patterns for AI agent systems, in four skills. The orchestrator: tool-calling loops that survive context pressure, pipelines with human checkpoints and resume, provider routing with fallback and…