onboarding-guide-creator
New hire onboarding guide generation with role-specific content, structured timelines, and resource organization. Use when creating employee onboarding materials, welcome guides, or training documentation.
What this skill does
# Onboarding Guide Creator Structured frameworks for creating comprehensive employee onboarding programs with role-specific content, timelines, and success metrics. ## Onboarding Timeline Framework ### Master Timeline ``` ONBOARDING PHASES: PRE-DAY-1 (Offer Accepted → Start Date) ├── Welcome email with logistics ├── Equipment ordering and setup ├── Account provisioning (email, Slack, tools) ├── Pre-reading materials sent ├── Buddy/mentor assigned └── First week calendar pre-populated WEEK 1: ORIENT ├── Day 1: Welcome, setup, team introductions ├── Day 2: Company overview, culture, values ├── Day 3: Role-specific training begins ├── Day 4: Tool training and access verification ├── Day 5: Week 1 check-in with manager └── Deliverable: "I understand my role and how the company works" WEEKS 2-4: LEARN ├── Deep-dive into team processes and workflows ├── Shadow key meetings and customer calls ├── Complete required compliance training ├── Begin first small project or task ├── Meet cross-functional stakeholders └── Deliverable: "I can execute core tasks with guidance" 30-DAY CHECK-IN ├── Manager 1:1 review ├── Self-assessment against 30-day goals ├── Feedback collection (new hire → company) ├── Identify knowledge gaps └── Adjust 60-day plan if needed DAYS 31-60: CONTRIBUTE ├── Own tasks and small projects independently ├── Contribute to team goals ├── Deeper cross-functional collaboration ├── Begin attending all recurring meetings └── Deliverable: "I can work independently on routine tasks" 60-DAY CHECK-IN ├── Progress review against goals ├── Expanded responsibilities discussion ├── Peer feedback collection └── Adjust 90-day plan if needed DAYS 61-90: OWN ├── Own a meaningful workstream or project ├── Contribute to planning and strategy discussions ├── Mentor newer team members if applicable ├── Identify process improvements └── Deliverable: "I am a fully productive team member" 90-DAY REVIEW ├── Formal performance discussion ├── Goal setting for next quarter ├── Onboarding feedback survey ├── Transition to standard performance cycle └── Celebrate completion ``` ## Role-Specific Templates ### Engineering Onboarding ``` ENGINEERING ONBOARDING ADDITIONS: PRE-DAY-1: - [ ] Dev machine ordered (spec: ___) - [ ] GitHub/GitLab access provisioned - [ ] VPN and SSH keys prepared - [ ] IDE license assigned WEEK 1: - [ ] Dev environment setup (follow setup guide) - [ ] Clone key repositories - [ ] Run the application locally - [ ] Review architecture documentation - [ ] Pair with buddy on a small bug fix - [ ] Understand CI/CD pipeline - [ ] Review coding standards and PR process WEEKS 2-4: - [ ] Complete first PR (small, well-scoped) - [ ] Participate in code review (as reviewer) - [ ] Attend sprint ceremonies - [ ] Understand on-call rotation and runbooks - [ ] Review incident response process - [ ] Deep-dive on owned service/module 30-DAY MILESTONE: - [ ] Merged 3+ PRs - [ ] Completed code review for others - [ ] Can run and debug the application locally - [ ] Understands deployment process 60-DAY MILESTONE: - [ ] Owns a feature or workstream - [ ] Can triage and fix production issues - [ ] Contributes to technical design discussions - [ ] Mentors on team conventions and tooling 90-DAY MILESTONE: - [ ] Delivered a meaningful feature end-to-end - [ ] Participated in on-call rotation - [ ] Contributed to team process improvements - [ ] Comfortable presenting technical work to team ``` ### Sales Onboarding ``` SALES ONBOARDING ADDITIONS: WEEK 1: - [ ] Product overview and demo walkthrough - [ ] ICP and buyer persona review - [ ] CRM setup and pipeline training - [ ] Sales methodology introduction - [ ] Listen to 5 recorded discovery calls - [ ] Review competitive battle cards WEEKS 2-4: - [ ] Shadow 10+ live calls (discovery, demo, close) - [ ] Complete product certification - [ ] Practice pitch delivery (recorded + feedback) - [ ] Learn objection handling frameworks - [ ] Understand pricing and discounting policies - [ ] Build initial target account list 30-DAY MILESTONE: - [ ] Pass product knowledge certification - [ ] Deliver solo demo to internal audience - [ ] Own 5+ accounts/opportunities - [ ] Complete CRM hygiene training 60-DAY MILESTONE: - [ ] Run discovery calls independently - [ ] Pipeline meets minimum threshold ($X) - [ ] Delivered 10+ demos - [ ] Comfortable with pricing discussions 90-DAY MILESTONE: - [ ] Closed first deal (or advanced to late stage) - [ ] Pipeline at quota-pace level - [ ] Can handle competitive objections confidently - [ ] Contributing to team best practices ``` ### Design Onboarding ``` DESIGN ONBOARDING ADDITIONS: WEEK 1: - [ ] Design tools setup (Figma, prototyping tools) - [ ] Review design system and component library - [ ] Brand guidelines deep-dive - [ ] Understand design review process - [ ] Meet key stakeholders (PM, Eng, Research) WEEKS 2-4: - [ ] Audit existing designs in your area - [ ] Shadow user research sessions - [ ] Complete first small design task - [ ] Present work in design critique - [ ] Understand handoff process to engineering 30-DAY MILESTONE: - [ ] Completed first design deliverable - [ ] Comfortable with design system usage - [ ] Participated in design critique (giving + receiving) - [ ] Understands user research insights for your area 60-DAY MILESTONE: - [ ] Owns a design workstream - [ ] Conducted or co-led user research - [ ] Designs are passing critique with minimal revision - [ ] Collaborating effectively with PM and engineering 90-DAY MILESTONE: - [ ] Delivered end-to-end design for a feature - [ ] Contributing to design system evolution - [ ] Presenting design rationale to stakeholders confidently - [ ] Identified and proposed design improvements ``` ### Operations Onboarding ``` OPERATIONS ONBOARDING ADDITIONS: WEEK 1: - [ ] Process documentation review - [ ] Tool access (project management, analytics, comms) - [ ] Org chart and RACI matrix review - [ ] Understand key workflows and SLAs - [ ] Meet cross-functional dependencies WEEKS 2-4: - [ ] Shadow key operational processes end-to-end - [ ] Document current-state processes you'll own - [ ] Identify quick-win improvements - [ ] Understand reporting cadence and metrics - [ ] Complete compliance and policy training 30-DAY MILESTONE: - [ ] Can execute core processes independently - [ ] Owns daily/weekly operational tasks - [ ] Documented one process improvement - [ ] Comfortable with reporting tools 60-DAY MILESTONE: - [ ] Owns a workstream end-to-end - [ ] Implemented at least one process improvement - [ ] Managing cross-functional dependencies - [ ] Contributing to operational metrics review 90-DAY MILESTONE: - [ ] Fully owns operational area - [ ] Driving efficiency improvements measurably - [ ] Presenting operational updates to leadership - [ ] Mentoring on processes for newer team members ``` ## Welcome Guide Structure ### Day 1 Welcome Document ``` WELCOME GUIDE OUTLINE: 1. WELCOME MESSAGE - Personal note from manager - Team welcome and excitement - What to expect on Day 1 2. COMPANY OVERVIEW - Mission and vision (one paragraph each) - Company history (brief timeline) - Products and customers (who we serve) - Business model (how we make money) - Org structure (high-level chart) 3. CULTURE AND VALUES - Core values with examples - Communication norms (async vs sync, tools) - Meeting culture (camera on/off, note-taking) - Work schedule expectations (hours, flexibility) - PTO and time-off culture 4. YOUR TEAM - Team mission and current priorities - Team members (name, role, fun fact) - Your buddy/mentor (name, how to reach) - Key stakeholders outside the team 5. TOOLS AND ACCESS - Account credentials and setup guide - Key tools checklist (with links) - IT support contact - Security policies (passwords, 2FA) 6. LOGISTICS - Office location / remote setup - Expense policy - Benefits enrollment deadline - HR contact for questio
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.