Map concept dependencies before you start studying a topic
Starting to study a topic without knowing what you need to know first is one of the most common reasons people get stuck or frustrated. This prompt builds a prerequisite dependency map so you study in the right order.
I want to learn {{TARGET_TOPIC}} but I keep hitting walls because I realize I'm missing foundational knowledge mid-way through resources.
My current background: {{CURRENT_BACKGROUND}}
My goal (what I want to be able to do): {{LEARNING_GOAL}}
1. Identify all the prerequisite concepts required to understand {{TARGET_TOPIC}} at the level needed for {{LEARNING_GOAL}}. List every concept that, if I didn't understand it, would block me.
2. Organize these prerequisites into a dependency map: which concepts must come before which. Present this as a numbered learning sequence, not a flat list. Indicate where concepts can be learned in parallel versus where strict ordering matters.
3. Given my background ({{CURRENT_BACKGROUND}}), mark each prerequisite as: (A) I likely already have this, (B) I may have this but should verify, or (C) I probably need to build this.
4. For the (C) prerequisites, estimate how long it would take someone with my background to get to working proficiency — be realistic and err on the side of more time, not less.
5. Flag any prerequisites that are commonly underestimated — things people skip because they seem basic, then struggle later.
6. Produce a recommended study sequence that starts from my actual current level and ends at {{LEARNING_GOAL}}.
Note: If {{TARGET_TOPIC}} is very broad (e.g., "machine learning"), this map will be large. Consider narrowing {{LEARNING_GOAL}} to a specific application to get a more useful, scoped dependency map. {{TARGET_TOPIC}}{{CURRENT_BACKGROUND}}{{LEARNING_GOAL}}
How to use this prompt
- Copy the prompt above (Copy button on the top-right).
- Replace each
{{VAR}}with your own value. Variables:{{TARGET_TOPIC}}{{CURRENT_BACKGROUND}}{{LEARNING_GOAL}}. - 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.