skills.rest
Community-Chests
Community-ChestsOFFICIAL
Explore all skills by this author →
GitHub

voluntary-exit

Coordinate member departures with handoffs, records, and data exports.

2|Updated Mar 13, 2026
Search Tags:#compliance#governance#data-export#voluntary-exit#departure-record#role-transfer
One-click install
npx skills add https://github.com/Community-Chests/neos-operating-system --skill voluntary-exit-community-chests
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: voluntary-exit
Source: https://github.com/Community-Chests/neos-operating-system/tree/main/neos-core/layer-10-exit/voluntary-exit
Command: npx skills add https://github.com/Community-Chests/neos-operating-system --skill voluntary-exit-community-chests

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Executes dignified member departures by coordinating handoffs, data export, and governance-record creation to preserve continuity and respect autonomy.

Core Features & Use Cases

  • Structured departure workflow: notification, commitment inventory, handoff, and Departure Record generation for audited governance history.
  • Data portability: exportable portable governance record to support re-entry or archival needs.
  • Neutral communications: independent coordination to minimize social pressure and maintain factual departure notices.

Quick Start

Initiate a standard 30-day voluntary exit for a member and generate the corresponding Departure Record and portable record.

Frequently Asked Questions about voluntary-exit

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

FAQPage Schema
How do I coordinate a voluntary exit and member departure workflow?▼

A voluntary exit coordinates member departures through notifications, commitment inventory, handoffs, and removal from agreements. It enforces a standard 30-day timeline to ensure complete records and continuity.

Can I generate a portable governance record for data export after a member leaves?▼

Yes, the voluntary exit process generates a portable governance record during departure. This data export supports re-entry or archival needs by preserving the member's audited governance history.

What is the standard timeline for completing a member handoff and departure record?▼

The standard timeline for a member handoff and departure record is 30 days. An accelerated 7-day urgent option is also available for faster exits requiring immediate commitment unwinding.

How does neutral communication work during a member departure?▼

Neutral communication during departure uses independent coordination to minimize social pressure. It maintains factual departure notices and ensures all handoff interactions remain objective and respectful.

What's the best way to unwind commitments and transfer roles when someone leaves?▼

The best way to unwind commitments is through structured role transfer during the departure workflow. It handles inventory checks, agreement removal, and generates a formal Departure Record for compliance.

Does the departure workflow support both individual exits and ecosystem-wide departures?▼

Yes, the departure workflow applies to both individual ETHOS exits and ecosystem-wide departures. It handles notifications, inventory, and data exports for any scale of member departure.

Related Skills

Explore More Content & Communication Skills→
Community-ChestsCommunity-Chests

commitment-unwinding

Coordinate systematic unwinding of departing members' commitments into a five-category ledger.

Official
Advanced
Community-ChestsCommunity-Chests

portable-record

Compile governance participation data into a portable YAML record with a cryptographic verification hash.

Official
Advanced
JadeZaherJadeZaher

voluntary-exit

Manage member departure with commitment handoff, data export, and formal record.

Community
Advanced
JadeZaherJadeZaher

re-entry-integration

Verify departure records and consent before reintegrating former ecosystem members.

Community
Advanced