b3os-team-member-lifecyclelisted

# b3rys Team Member Lifecycle Use this skill for team-member onboarding(영입), offboarding(퇴사/비활성화), runtime migration(실행 환경 이전), and lifecycle dry-runs. ## Onboarding(영입) — do NOT execute this file's checklist **The recruit flow is documented in full elsewhere, and that documentation is the current one. Go there first.** | What you need | Where | |---|---| | The recruit flow itself — dashboard wizard **and** API, OT stages, pairing | `skills/b3os/references/recruit.md` | | Runtime prerequisites — install, auth, what preflight actually checks | `skills/b3os/references/runtime-setup.md` | | A member that joined but won't answer | `skills/b3os/references/troubleshooting.md` | Fastest path is the dashboard: **Settings ▸ + 영입**. One form takes `id`, name, role, runtime, mention aliases and persona together; the bot token and the rest are collected during provisioning. For BYO runtimes (Hermes / OpenClaw) the runtime picker shows a setup link — **follow it before recruiting.** Preflight blocks activation until that runtime's auth exists, and finding that out mid-recruit wastes a cycle. The numbered onboarding steps further down are a **policy checklist, not a procedure**: read them for the gates the recruit flow does not decide for you (owner routing, context visibility, approval boundaries). Authoritative context — note which of these a fresh clone actually has: | File | Present in a fresh clone? | |---|---| | `<repo>/rules/SHARED.md` | yes | | `<repo>/rules/TEAM-OS.md` |