← ClaudeAtlas

coven-parallel-worklisted

Coven Parallel Work Protocol — how to use it from inside an OpenClaw familiar so multiple agents (Codex, Claude Code, Nova, Hermes, etc.) can share a repo without overwrites or clashes. The protocol itself is harness-agnostic; this skill is the OpenClaw entry point.
OpenCoven/coven · ★ 47 · AI & Automation · score 76
Install: claude install-skill OpenCoven/coven
# Coven Parallel Work Protocol — OpenClaw entry point ## What this is The **Coven Parallel Work Protocol** is a portable, harness-agnostic contract for safely running multiple agents on the same git repo on the same machine. It works for Codex, Claude Code, OpenClaw, Hermes, Nova, and any future runtime — anyone who runs `git`. This skill file is the **OpenClaw familiar's entry point**: it tells you when to use the protocol from inside an OpenClaw session, the local prototype tooling available, and the daily workflow. For the full spec (harness-agnostic, no OpenClaw assumptions), read [`PROTOCOL.md`](./PROTOCOL.md) — that's the contract any conforming implementation must respect. ## Where this lives - **Spec**: [`PROTOCOL.md`](./PROTOCOL.md) (in this directory; portable, will move upstream) - **Reference prototype**: POSIX-shell scripts in `~/.openclaw/workspace/bin/cv-wt`, `cv-claim` and hook templates in this directory's `hooks/` - **Canonical implementation (target)**: `OpenCoven/coven` — surfaced eventually as `coven wt`, `coven claim`, `coven hooks install`. **Not yet built.** Tracked upstream in [issue #167](https://github.com/OpenCoven/coven/issues/167). - **This skill**: how an OpenClaw familiar uses the protocol day-to-day The local prototype is intentionally a prototype. It's working code that respects the spec, sized to fit one user's setup. Once the canonical Coven implementation lands, this skill will redirect to it and the prototype scripts will become a