hoavdc/CodexKit / skills/codexkit-onboarding-plan-creator
codexkit-onboarding-plan-creator
VerifiedCreate structured employee onboarding plans using the 30-60-90 day framework aligned with SHRM best practices. Cover pre-boarding, Day 1, Week 1, and monthly milestones with task owners, success criteria, and buddy assignments. Use when hiring new employees or revamping the onboarding process.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 5.3 KB |
| agents/openai.yaml | config | 172 B |
| examples/common-mistakes.md | markdown | 802 B |
| examples/good-output.md | markdown | 890 B |
| verification/checklist.md | markdown | 1.4 KB |
verification/checklist.md
View on GitHub# 4C Verification Checklist — Onboarding Plan Creator
> Use this checklist after generating output. Answer each question honestly.
## Correctness — Is it right?
- [ ] Day-by-day schedule matches the role's actual ramp expectations
- [ ] Tool access and account provisioning checklist is complete for the role
- [ ] 30-60-90 milestones are achievable by someone at the expected level
## Completeness — Is it done?
- [ ] Covers all phases: pre-arrival, Week 1 (orientation), Month 1 (learning), Month 2-3 (contributing)
- [ ] Buddy/mentor assignment is included with clear expectations
- [ ] Culture, process, and technical onboarding are all addressed
## Context-fit — Does it match?
- [ ] Onboarding intensity matches the role seniority (senior hires need less hand-holding, more context)
- [ ] Remote vs in-person logistics are addressed appropriately
- [ ] Department-specific content is included alongside company-wide orientation
## Consequence — Is it safe to use?
- [ ] If the new hire follows this plan exactly, will they be productive by Day 30?
- [ ] If the buddy is unavailable for a week, does the plan still work?
- [ ] If a critical tool access is delayed, are workarounds documented?
---
**Final question:** _If this output were used immediately in production, what is the single biggest risk?_
Write the answer here before considering the skill output complete.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 469k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |