role-transfer

Coordinate governance-role transfers with handover checklists, overlap periods, and consent workflows.

2|Updated Mar 13, 2026

Search Tags:#governance #handover #audit-trail #consent #stakeholder-notification #role-transfer #domain-contract

Ready to run

npx skills add https://github.com/Community-Chests/neos-operating-system --skill role-transfer-community-chests

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: role-transfer
Source: https://github.com/Community-Chests/neos-operating-system/tree/main/neos-core/layer-02-authority/role-transfer
Command: npx skills add https://github.com/Community-Chests/neos-operating-system --skill role-transfer-community-chests

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This skill ensures structured, lossless transitions of governance roles by formalizing handover documents, overlap periods, and consent workflows so critical knowledge, commitments, and authorities are preserved during transitions.

Core Features & Use Cases

Structured handover artifacts: handover checklist, transfer records, domain contracts, and relationship maps to capture knowledge during a role change.
Overlap and consent mechanics: minimum overlap period, formal consent from assigning body, and authoritative transfer of assignment records.
Auditable provenance: end-to-end trail with post-transfer check-ins and notifications to adjacent domains, enabling governance continuity across voluntary, rotational, or reassignment transfers.

Quick Start

Begin the handover by completing the handover checklist and initiating the overlap with the incoming steward.

Frequently Asked Questions about role-transfer

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

FAQPage Schema

How do I structure a governance role handover to preserve knowledge and authority?▼

A structured governance role handover requires a handover checklist, transfer records, and relationship maps. You must establish an overlap period for the incoming steward and capture domain contracts to ensure lossless knowledge and authority transfer.

What is needed for an auditable role transfer provenance trail?▼

Auditable role transfer provenance requires end-to-end transfer records, assignment updates, and notifications to adjacent domains. A 30-day post-transfer check-in ensures governance continuity and verifies the handover artifacts are actively maintained.

Does a voluntary role reassignment require formal consent and an overlap period?▼

Yes, voluntary role reassignments require formal consent from the assigning body and a minimum overlap period. These mechanics guarantee authoritative transfer of assignment records and preserve commitments during domain role changes.

How do I notify adjacent domains during a stakeholder role transition?▼

Notify adjacent domains during a stakeholder role transition by generating stakeholder notifications through the transfer workflow. This maintains governance continuity and updates relationship maps to reflect the new domain authority.

What is the best way to document domain contracts during a role rotation?▼

Document domain contracts during a role rotation by updating transfer records and handover artifacts. Capturing these commitments ensures the incoming steward receives authoritative assignment records and clear governance boundaries.

When should I use a formal consent workflow for a role transfer?▼

Use a formal consent workflow for any governance role transfer, including voluntary handovers, rotations, or reassignments. It ensures the assigning body authorizes the transition and validates the handover checklist before the overlap period ends.