Design a focused reading list for onboarding to a new domain
When you move into an unfamiliar domain — new industry, new function, new tech stack — a pile of links helps no one. This prompt builds a sequenced reading plan with explicit rationale for each item's order and purpose.
I'm onboarding to {{NEW_DOMAIN}} as a {{JOB_ROLE}}. I need to be functional enough to contribute in {{TIMEFRAME}} (e.g., 2 weeks, 30 days). My existing background is {{EXISTING_BACKGROUND}}.
1. Identify the 4-5 core concepts someone must understand to operate in {{NEW_DOMAIN}}. For each, write one sentence explaining why it's foundational and what goes wrong if you skip it.
2. Build a sequenced reading plan with exactly 8 items total. Each item should be:
- A type of source (e.g., 'official documentation overview', 'practitioner post-mortem', 'introductory textbook chapter', 'annotated worked example') rather than a specific URL or book title (links go stale; source types don't).
- Labeled with its position in the sequence and a reason it belongs at that position.
- Matched to one of the core concepts from step 1.
- Accompanied by a guiding question I should be able to answer after reading it.
3. Flag 2 common onboarding mistakes people make when learning {{NEW_DOMAIN}} on their own (e.g., going too deep on theory before touching practice, ignoring naming conventions that cause confusion later).
4. Suggest one low-stakes practical exercise I can do after item 4 to pressure-test my understanding before continuing.
Note: This plan is for orientation, not mastery. If {{TIMEFRAME}} is shorter than 2 weeks, tell me which 4 items to prioritize and which to defer. {{NEW_DOMAIN}}{{JOB_ROLE}}{{TIMEFRAME}}{{EXISTING_BACKGROUND}}
How to use this prompt
- Copy the prompt above (Copy button on the top-right).
- Replace each
{{VAR}}with your own value. Variables:{{NEW_DOMAIN}}{{JOB_ROLE}}{{TIMEFRAME}}{{EXISTING_BACKGROUND}}. - Paste it into one of the recommended tools below.
- Iterate: tighten constraints in the prompt if the output is generic.
Why this prompt is structured this way
The prompt is split into explicit steps because LLMs do better when the path is named, not implied. Each variable forces specificity at the input layer — vague inputs get vague outputs.
Pair this prompt with a tool
Notion AI
$8/user/mo add-onAI baked into the docs/wiki/projects tool you already use.
Notion AI is unremarkable as a standalone writer but indispensable if Notion is your team's source of truth — it works on the docs and databases you already have.
Perplexity
$0/mo (Pro at $20)AI search engine with citations.
Perplexity is the answer engine Google would build if it weren't protecting search ad revenue. Cited answers, follow-up questions, focused source modes.
Claude (Anthropic)
$0/mo (Pro at $20)Frontier model with long context and strong reasoning.
Claude (Opus / Sonnet / Haiku tiers) is the assistant favored by writers and engineers who care about reasoning quality and tone. 1M token context on Opus.
ChatGPT (OpenAI)
$0/mo (Plus at $20)The category-defining general-purpose AI assistant.
ChatGPT has the broadest feature surface: image gen, voice, custom GPTs, web browsing, code execution. Often the right default; sometimes beaten on specific tasks by Claude or Perplexity.
The PlaybookPrompts weekly
One short email per week. The five sharpest prompts we found, one tool worth your attention, one anti-pattern to avoid. Unsubscribe in one click.
Newsletter signup is not configured. Set PUBLIC_NEWSLETTER_USERNAME in the build env.