Menu
Claim or release OBPI-level work locks for multi-agent coordination. Use when claiming an OBPI before starting work, releasing a lock after completing or abandoning work, or checking which OBPIs are currently claimed by agents.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | gz-obpi-lock |
| persona | main-session |
| description | Claim or release OBPI-level work locks for multi-agent coordination. Use when claiming an OBPI before starting work, releasing a lock after completing or abandoning work, or checking which OBPIs are currently claimed by agents. |
| category | obpi-pipeline |
| lifecycle_state | active |
| owner | gzkit-governance |
| last_reviewed | "2026-07-26T00:00:00.000Z" |
| metadata | {"skill-version":"6.2.0"} |
| model | haiku |
Claim or release OBPI-level work locks for multi-agent coordination.
These thoughts mean STOP — you are about to bypass coordination:
| Thought | Reality |
|---|---|
| "No one else is working on this, I don't need to lock" | You do not know what other agents are doing. The lock is coordination, not permission. |
| "I'll just do a quick fix, no need for a lock" | Quick fixes that conflict with another agent's work create merge conflicts. Lock first, always. |
| "The lock expired, so I'll just re-claim it" | An expired lock may mean another agent started work. Check status before re-claiming. |
| "I'll release the lock manually later" | The pipeline releases at Stage 5. Manual release outside the pipeline risks orphaned work. |
| "Lock conflicts slow me down" | Merge conflict resolution after concurrent edits is far slower than waiting for a lock. |
gz obpi lock claim in the session/gz-obpi-lock claim OBPI-0.0.25-03
/gz-obpi-lock release OBPI-0.0.25-03
/gz-obpi-lock status # show all locks
/gz-obpi-lock status ADR-0.0.25 # show locks for one ADR
File-based locks in .gzkit/locks/ (gitignored — local coordination only).
Path: .gzkit/locks/obpi/{OBPI-ID}.lock.json
{
"obpi_id": "OBPI-0.0.25-03",
"agent": "claude-code",
"pid": 12345,
"session_id": "abc123",
"claimed_at": "2026-02-14T12:00:00Z",
"branch": "master",
"ttl_minutes": 120
}
uv run gz obpi lock claim OBPI-X.Y.Z-NN
uv run gz obpi lock claim OBPI-X.Y.Z-NN --ttl 240
uv run gz obpi lock claim OBPI-X.Y.Z-NN --json
Exit code 0 = claimed, 1 = conflict (another agent holds it).
uv run gz obpi lock release OBPI-X.Y.Z-NN
uv run gz obpi lock release OBPI-X.Y.Z-NN --json
uv run gz obpi lock release OBPI-X.Y.Z-NN --force # abort/handoff — bypass ownership check
Exit code 0 = released (or no lock found), 1 = ownership error (without --force).
uv run gz obpi lock check OBPI-X.Y.Z-NN
uv run gz obpi lock check OBPI-X.Y.Z-NN --json
Exit code 0 = held (prints holder info), 1 = free.
uv run gz obpi lock list
uv run gz obpi lock list --adr ADR-X.Y.Z
uv run gz obpi lock list --json
Agents identify themselves by environment:
| Signal | Agent |
|---|---|
CLAUDE_CODE env var or Claude Code runtime | claude-code |
CODEX_SANDBOX env var | codex |
| VS Code Copilot context | copilot |
| Fallback | unknown-{PID} |
The pipeline calls uv run gz obpi lock claim at Stage 1 (Load Context) and uv run gz obpi lock release at Stage 5 (Sync). On any abort or handoff, the pipeline releases the lock via uv run gz obpi lock release {OBPI-SLUG} --force to prevent orphaned locks.
Files known to cause multi-agent conflicts:
| File Pattern | Conflict Type | Mitigation |
|---|---|---|
docs/design/adr/*/adr_status.md | ADR status table | Regenerate via /gz-adr-sync |
**/logs/obpi-audit.jsonl | Append-only ledger | JSONL merge driver (see below) |
docs/design/adr/**/*.md (status field) | Brief status | Lock prevents concurrent edits |
.gzkit/insights/agent-insights.jsonl | Append-only log | JSONL merge driver |
For append-only JSONL files, conflicts are resolvable by union merge:
Add to .gitattributes:
*.jsonl merge=union
The merge=union strategy keeps lines from both sides, which is correct for append-only ledgers.
Before pushing, agents should verify no divergence on shared files:
# Check if shared governance files have diverged from remote
git fetch origin
git diff --name-only origin/main..HEAD | grep -E '(adr_status|obpi-audit\.jsonl|agent-insights\.jsonl)'
If shared files appear in the diff, the agent should:
/gz-adr-sync, /gz-obpi-sync)For heavy parallel workloads, each agent can use a separate git worktree:
# Create agent-specific worktree
git worktree add ../gzkit-claude-code -b agent/claude-code/obpi-0.0.25-03
# Work in the worktree
cd ../gzkit-claude-code
# Merge back
cd ../gzkit
git merge agent/claude-code/obpi-0.0.25-03
git worktree remove ../gzkit-claude-code
When to use worktrees:
When NOT to use worktrees:
gz obpi lock claim (Stage 1), gz obpi lock release (Stage 5)/gz-session-handoff (preserves lock context)AGENTS.md § Agent ProfilesValidate and stage a candidate rendition from the corpus via gz content compose. Use when the agent has made compression decisions (drop/combine/rewrite of compressible corpus entries toward the declared setpoint) and wants the tool to validate invariant-floor compliance, compute byte evidence, write the candidate artifact, and emit a ledger event.
Enter and exit the MX Maintenance Hangar — operator's interface to gz mx. Use when entering the hangar to perform governance repair, checking hangar status mid-session, or cleanly exiting when repair is complete. Operator operates the skill; the skill invokes gz mx; nobody shells out.
Create and resume session handoff documents for agent context preservation across engineering sessions.
Create and resume session handoff documents for agent context preservation across engineering sessions.
Collaborative design dialogue that produces GovZero ADR artifacts. Use when exploring a new feature, capability, or architectural change before implementation — replaces superpowers brainstorming for this project. Triggers on "design X", "let's design", "brainstorm X", "I want to build X", "gz-design".
Cross the airlock membrane — the entry/exit gate every unit of work passes through (ADR-0.33.0). Use to inspect a target's seam-map before touching it (`gz airlock in`), account for what a transit disturbed (`gz airlock out`), or make a governed ad-hoc reconnaissance entry with light repair at most (`gz permitted-entry`). Diagnostic-only for now — a staged posture, not the declared end state; never writes L1 canon.