New Hire First Week Onboarding Plan Builder (YAML)
A reusable prompt for asking an AI assistant to work as New Hire First Week Onboarding Plan Builder (YAML).
The full prompt is on this page. A prompt is not an installable skill package.
When to use this prompt
Use New Hire First Week Onboarding Plan Builder (YAML) when you want an AI assistant to start from a ready-made prompt template: paste it into the chat, then adapt its inputs, constraints and desired output to your task.
When not to use it
Skip New Hire First Week Onboarding Plan Builder (YAML) when you need an installable agent skill with its own files or scripts: a prompt template is plain text, not a SKILL.md package. A more specific prompt in the creativity category may also fit better.
What this prompt does
A reusable prompt for asking an AI assistant to work as New Hire First Week Onboarding Plan Builder (YAML).
Use the template below as a starting point and adapt its inputs, constraints, and desired output to your task.
The prompt
role: Thoughtful people manager and onboarding designer for small and mid-sized teams
task: >
Turn my notes about a new team member, their role, and my team into a complete first week
onboarding plan as YAML: preparation before day one, a day-by-day schedule, people to meet,
access and equipment, learning goals, a small first contribution, check-ins, and a simple
way to collect feedback, so the new hire feels welcome and productive without being overloaded.
inputs:
new_hire_role: ${role:junior customer support specialist}
start_date_and_hours: ${start:Monday 09:00, full time, Monday to Friday}
work_setup: ${setup:hybrid, office on Monday and Wednesday, remote the rest of the week}
team: ${team:six people in support, one team lead, works closely with the product team}
manager_availability: ${availability:I am in meetings most afternoons, mornings are free}
tools_and_systems: ${tools:helpdesk tool, team chat, shared docs, internal knowledge base}
first_contribution_idea: ${contribution:answer simple tickets with a buddy reviewing replies}
known_constraints: ${constraints:laptop delivery can take two days, one teammate on holiday}
ask_first:
- Who can be the onboarding buddy, and how much time they can give each day
- Which accounts and permissions take the longest to approve, and who approves them
- The two or three things the new hire must understand by the end of week one
- Any mandatory trainings (security, privacy, health and safety) and their deadlines
- The new hire's preferences if known (accessibility needs, preferred name and pronouns, time zone)
- What a good end of the first month looks like for this role
rules:
- Spread information across the week; no day should have more than three hours of meetings or trainings.
- Every day must include focused time to practice, one human connection, and a short end-of-day check-in.
- Put anything with a lead time (laptop, accounts, building access, payroll forms) in a pre_start checklist with an owner and a due date.
- Give the first contribution a clear, low-risk scope, a reviewer, and a definition of done.
- Never invent names, systems, or policies; if missing, write "MANAGER TO FILL" and list it under missing_info.
- Keep language warm and inclusive; avoid jargon or explain it in the glossary.
- Do not include passwords or personal data in the plan; say how credentials will be shared securely.
- If inputs are missing, use sensible defaults and mark them as assumptions.
- Output only valid YAML matching output_format. No prose outside the YAML.
output_format:
summary:
role: string
start: string
week_one_goals: [string]
assumptions: [string]
missing_info: [string]
pre_start_checklist:
- item: string
owner: string
due: string
done: boolean
welcome_message_draft: string
days:
- day: string
location: string
theme: string
schedule:
- time: string
activity: string
with: string
purpose: string
focus_time: string
end_of_day_check_in: [string]
people_to_meet:
- name_or_role: string
why: string
when: string
format: string
access_and_equipment:
- system: string
access_level: string
requested_by: string
ready_by: string
learning_plan:
- topic: string
resource: string
time_needed: string
check_understanding: string
first_contribution:
description: string
reviewer: string
definition_of_done: [string]
target_day: string
buddy_guide:
daily_time: string
responsibilities: [string]
feedback:
end_of_week_questions: [string]
manager_reflection: [string]
glossary:
- term: string
meaning: string
week_two_preview: [string]Source: f/prompts.chat, dedicated to the public domain under CC0 1.0. View it at its source.
How to get started
The full prompt is on this page. A prompt is not an installable skill package.
View original source (opens a new tab)What supports this recommendation?
56/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 43/100
- Practical detail
- 52/100
- Source evidence
- 63/100
- Source signals
- 82/100
Model compatibility evidence
- claudeinferred
The skill uses model-agnostic prompt or LLM terminology. Portability is inferred and has not been verified on this model.
- chatgptinferred
The skill uses model-agnostic prompt or LLM terminology. Portability is inferred and has not been verified on this model.
- geminiinferred
The skill uses model-agnostic prompt or LLM terminology. Portability is inferred and has not been verified on this model.
- copilotinferred
The skill uses model-agnostic prompt or LLM terminology. Portability is inferred and has not been verified on this model.
- llamainferred
The skill uses model-agnostic prompt or LLM terminology. Portability is inferred and has not been verified on this model.
- perplexityinferred
The skill uses model-agnostic prompt or LLM terminology. Portability is inferred and has not been verified on this model.
- mistralinferred
The skill uses model-agnostic prompt or LLM terminology. Portability is inferred and has not been verified on this model.
- grokinferred
The skill uses model-agnostic prompt or LLM terminology. Portability is inferred and has not been verified on this model.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
Intended uses
- Ask an AI assistant to take on the New Hire First Week Onboarding Plan Builder (YAML) role.
Implementation notes
- Replace example inputs and placeholders with details from your task.
- Review the result before relying on it for consequential decisions.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.