/onboard procedure: read roster + team-memory + posture + claims + codify lease + rules-changed for a new operator joining a multi-operator COC repo.

Compile operator identity, roster, team-memory, posture, claims, and lease into a read-only briefing.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/terrene-foundation/kailash-coc-claude-rb --skill onboard-procedure-read-roster-team-memory-posture-claims-codify-lease-rules-changed-for-a-new-operator-joining-a-multi-operator-coc-repo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: /onboard procedure: read roster + team-memory + posture + claims + codify lease + rules-changed for a new operator joining a multi-operator COC repo.
Source: https://github.com/terrene-foundation/kailash-coc-claude-rb/tree/main/.claude/skills/41-onboard
Command: npx skills add https://github.com/terrene-foundation/kailash-coc-claude-rb --skill onboard-procedure-read-roster-team-memory-posture-claims-codify-lease-rules-changed-for-a-new-operator-joining-a-multi-operator-coc-repo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Multi-operator Claude Code repos struggle with reliable onboarding because new operators need a consistent snapshot of identity, roster, posture, claims, and the codify lease without accidentally proceeding on stale or unverified state.

Core Features & Use Cases

  • Read-only, deterministic briefing: Produces a structured onboarding runbook that reads operator identity, roster, team-memory, active workspace, posture, adjacency claims, codify lease status, and rules changes without writing any state.
  • Integrity-guarded team-memory handling: Validates each team-memory entry’s integrity, surfaces failures explicitly (including an empty failed_integrity section), and skips superseded facts.
  • Operational safety gates: Blocks onboarding continuation when identity is blocked, surfaces pending_verification acknowledgements, and prevents concurrent /codify by checking the active codify lease.
  • Rules-changed verification support: Detects and enumerates modified MUST clauses candidates for pending verification.

Quick Start

Use the /onboard skill in your first multi-operator session to generate a full read-only snapshot of operator identity, team state, posture, active claims, codify lease status, and required acknowledgements.

Frequently Asked Questions about /onboard procedure: read roster + team-memory + posture + claims + codify lease + rules-changed for a new operator joining a multi-operator COC repo.

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

FAQPage Schema
How do I onboard a new operator to a multi-operator Claude Code repository?

To onboard a new operator, use a deterministic read-only procedure that compiles identity, roster, team-memory, posture, claims, and codify lease status into a stable briefing without writing any state.

What is team-memory integrity validation during operator onboarding?

Team-memory integrity validation checks each memory entry for consistency, explicitly surfaces failures in a dedicated section, and skips superseded facts to prevent proceeding on stale or unverified state.

How do I handle codify lease contention when a new operator joins?

Codify lease contention is handled by operational safety gates that check the active lease status, preventing concurrent codify operations and blocking onboarding continuation when lease contention or pending verifications exist.

When should I run an operator onboarding snapshot in a multi-operator repo?

Run an operator onboarding snapshot when a new operator joins, after session clearing or auto-compaction, or before codifying when lease contention and pending verifications must be handled.

Can I get structured JSON output for operator onboarding state?

Yes, structured JSON output is available in --json mode, providing a stable schema that includes operator identity, team state, posture, active claims, codify lease status, and required acknowledgements.

Why does onboarding block when identity verification fails?

Onboarding blocks on failed identity verification because strict fail-closed behavior is enforced, ensuring typed errors are surfaced and preventing operators from proceeding without validated identity and pending verifications.