Offboarding & Exit

Plan a dated departure checklist with a named owner and an agreed last working day. The skill records access, equipment, handover and final-pay checkpoints. It builds empty exit templates on request.

The skill separates advice, review, conversion and build requests before producing artifacts. Advice receives a short recommendation and an offer of a relevant build. An explicit build request proceeds once essential missing facts are resolved. It asks one question at a time, reuses answers already supplied and stops when further answers would not change the deliverable. Unknown information remains unknown rather than receiving invented values.

Use it for an offboarding checklist, exit interview tracker or employee departure process. Establish the exit type, last day, process owner, equipment return and account-closure timing.

It does not revoke access, terminate employment or provide legal advice about an exit. Record the exit reason while feedback can still be requested, and leave sensitive decisions to a qualified reviewer. The skill does not calculate payroll, tax, leave balances or KPIs. Automation, reminders and synchronization require an integration layer. Legal, tax and HR review is required before templates drive real decisions.

The workflow is exit agreed, checklist started, access and equipment closed, final pay confirmed, then exit recorded and reviewed. Its 18 fields are Exit Record, Employee Name, Department, Manager, Exit Type, Notice Date, Last Working Day, Reason, Handover Owner, Knowledge Transfer Done, Assets Returned, Access Removed, Accounts to Close, Final Settlement Done, Exit Interview Done, Rehire Eligible, Status and Exit ID. Exit types include Resignation, Termination, Retirement, End of Contract and Other; statuses are Initiated, In Progress, Completed and Cancelled. No relation fields are specified. Inputs determine whether a checklist, exit record or reporting structure is needed.

Requested artifacts can include CSV, SQL DDL, JSON Schema, Notion property mappings or an Excel workbook. The formats derive from one field list: CSV and JSON retain matching display names, while SQL uses normalized identifiers. Dates retain date types, money retains currency types and cross-table references retain relation types. Select options are a starting set that can be renamed to match the business.

One SQL example is:

CREATE INDEX idx_offboarding_exit_status ON offboarding_exit (status);

Templates are empty by default. Example rows are produced only on request and remain obviously synthetic. Sensitive identifiers should not be repeated unnecessarily during a requested review. Machine-readable data stays separate from explanatory prose and any material validation failures. Excel-compatible CSV uses UTF-8 with a byte order mark and accompanying guidance about number, date and currency columns. An XLSX workbook is a separate requested output rather than a renamed CSV.

The Notion output routes to notion-manual-import for CSV, property mappings, import steps and verification. Manual mappings require no connection. Requested live workspace changes require actual tool access, a verified target and authorization. Imported columns may initially be Text and need their mapped property types applied. Relation links resolve after both relevant databases are imported. A static mapping alone does not establish a completed workspace change.