{
  "schema": "leumas.docs.page/1",
  "id": "adapter:domain/onboarding-planner",
  "slug": "adapters/domain/onboarding-planner",
  "kind": "capabilities",
  "bucket": "package",
  "title": "onboarding-planner",
  "name": "Onboarding Planner",
  "eyebrow": null,
  "chip": null,
  "summary": "New-hire onboarding, employee ramp-up and first-90-days planning capability pack for managers, HR, people-ops and team leads: generate a structured 30/60/90-day onboarding plan (plan) for any role...",
  "keywords": [
    "onboarding-planner",
    "new-hire",
    "ramp-up",
    "first-90-days",
    "people-ops",
    "goals",
    "preboarding",
    "week-1"
  ],
  "audience": "both",
  "funnel": {
    "product": null,
    "cta": null
  },
  "body": "# onboarding-planner\n\nNew-hire onboarding & first-90-days pack. Role-aware templates for managers, HR and team leads, with\nan optional AI layer that tailors output to a specific role/team/company when a model is reachable\n(and falls back to the deterministic template otherwise).\n\n**Guidance templates, not HR or legal advice.**\n\n## Tools\n\n| Tool | Args | Does |\n|---|---|---|\n| `plan` | `{role, level?, name?, team?, options?}` | 30/60/90-day plan with learn → contribute → own phases. `options.remote` remote-first; `options.tailor` requests AI tailoring. |\n| `checklist` | `{role, name?, phase?, options?}` | Preboarding + week-1 checklist. `phase`: `preboarding` \\| `week1` \\| `all`. `options.remote` swaps in ship-hardware steps. |\n| `milestones` | `{role, startDate?, options?}` | Ramp milestones (day 1 → 90) with success criteria; real target dates when `startDate` (ISO) is given. |\n| `buddyPlan` | `{role, name?, options?}` | Buddy/mentor program: cadence, touchpoints, responsibilities, success signals. |\n| `resourcesList` | `{role, team?, options?}` | Curated docs/tools/people/learning list; `options.tailor` adds AI suggestions. |\n| `listRoles` | `{}` | Roles with dedicated templates + aliases. |\n\nRoles: software engineer, designer, product manager, sales, marketing, support, data scientist,\nmanager, plus a generic default. Unknown roles resolve to the generic template.\n\n## Example\n\n```js\nimport pack from './index.js';\npack.adapters.plan({ role: 'software engineer', name: 'Ada', team: 'Platform', level: 'senior' });\n// { mode:'heuristic', role:'Software Engineer', phases:[{window:'Days 1-30',theme:'Learn & assess',goals:[…]}, …] }\n\npack.adapters.milestones({ role: 'designer', startDate: '2026-08-01' });\n// milestones with targetDate on each, fullyProductiveBy:'2026-10-29'\n```\n\n## DRY boundaries\n\n- **`datetime`** owns raw date arithmetic; **`cron`** owns recurring-cadence parsing. This pack composes\n  people-ops onboarding *templates* (plans, checklists, milestones, buddy programs) none of those own.\n- Self-contained: only cross-pack import is `../_shared/llm.js`.\n\n## Hybrid intelligence\n\nAll cores are pure templates that run offline. `plan` and `resourcesList` accept `options.tailor:true`\nto request LLM tailoring; with no model reachable they return the template with `mode:'heuristic'`. A\ndown model never throws.\n",
  "source": {
    "path": "shared/engines/adapters/domain/onboarding-planner/README.md",
    "blobSha": "",
    "commit": "",
    "committedAt": "",
    "provenance": "no-git",
    "bytes": 2560,
    "hash": "4c200c6edfd7cd6dca68db34869f36fb9a1314ad"
  },
  "urls": {
    "html": "/p/adapters/domain/onboarding-planner",
    "json": "/docs/adapters/domain/onboarding-planner.json",
    "md": "/docs/adapters/domain/onboarding-planner.md"
  },
  "links": {
    "composes": [],
    "usedBy": [],
    "product": [],
    "howTo": [],
    "skills": []
  }
}
