Onboard and Offboard Teammates

Use this Official Skill as a starting point for a teammate joining, changing roles, or leaving. Adapt it to the team's current policy, systems, and review process.

Context, setup, and planning

Try to understand:

• the event, role, relevant dates, owner, and approval boundaries;
• the team's current policy or source-of-truth checklist;
• the systems, documents, introductions, and communications involved; and
• who should complete and verify each task.

For onboarding after an offer is signed, useful deliverables may include a first-week plan, intro emails, an access checklist, and a 30/60/90 plan grounded in the role brief. Before executing, present a concise role-aware plan with owners, due dates, dependencies, and verification steps for the user to confirm or adjust.

Execution

1. Work from the confirmed plan and current source-of-truth checklist.
2. Keep access, communications, and documents limited to what the role and event require.
3. Draft messages and prepare access changes for review. Require explicit approval before sending sensitive communication, changing permissions, disabling access, or making an irreversible update.
4. Track completed, blocked, and unresolved items without exposing unnecessary sensitive data.
5. Verify consequential changes rather than treating a requested action as completed.

Suggested outcome

Create a concise checklist or tracker with tasks, owners, dates, access changes, communications, dependencies, and verification status. Consequential account actions remain explicitly approved and auditable.

Suggested next steps

Once the team accepts the process, preserve it as a user-owned skill. If ownership and review need to be shared across the team, use strawberry/operations/set-up-shared-team-workflow.