Here’s a quick gut check: think about the last research paper you finished. Could you explain the main finding right now, without peeking? Most people can’t, and it’s not because they didn’t understand it the first time. A second-year chemistry PhD student who posted this in r/PromptEngineering, u/Ok_Layer_1947, hit that exact wall over and over: finish a paper, feel confident, close the tab, and then a week later can’t reconstruct more than a vague impression of what it actually said. The fix wasn’t reading more carefully or taking better notes in the margins. It was testing instead of re-reading, and the author packaged the whole thing into a two-step prompt so you don’t have to write your own quiz questions from scratch every time.
Here’s the trick worth stealing: the prompt runs in the same chat, once before you read and once after. That’s it. No flashcards, no separate app, no spaced-repetition system to maintain, just a habit bolted onto reading you’re already doing anyway.
Step 1: Guess Before You Read 🎯
Before you open the paper, drop this into your chat, filling in the title and abstract:
“I’m about to read this paper: {{title / abstract}}. Based only on the abstract, ask me one question: what do I expect the main finding and method to be? Wait for my guess. Don’t tell me if I’m right yet.”
Answer honestly, even if your guess feels shaky or half-formed. That’s the point. You’re planting a stake in the ground so you have something to measure against later. Say the abstract mentions a new catalyst for a reaction you vaguely recognize. Your guess might be completely wrong on the mechanism and still be useful, because now you’re reading to check a specific claim instead of just absorbing text in order.
Step 2: Test Yourself After 🧠
Once you’ve actually finished reading, paste this into the same conversation:
“Now I’ve read it. Without me looking back at the paper, ask me three questions ONE at a time: 1. What was the actual main finding, and how did my earlier guess compare? 2. What was the key method, and what’s one weakness of it? 3. Where could this apply to something outside the paper’s own topic? After each answer, tell me what I missed in one line. At the end, list the specific things I couldn’t recall so I know what to re-read.”
No looking back at the PDF while you answer. That’s the uncomfortable part, and the author is right that it’s exactly why it works. The gap between what you think you remember and what you can actually produce on demand is where the real learning happens, not in the smooth first pass through the text.
What Your Answers Actually Mean 🔍
One commenter, u/Adventurous_Sport613, called the before-reading guess “such a clever hook,” and that’s really the engine behind this whole thing. Guessing first gives your brain a prediction to check against, so when the real finding lands, it either confirms or corrects something specific instead of washing past you as one more fact in a pile of facts. Struggling with question 3, the outside-the-topic application, usually means you understood the paper’s own claims but haven’t built a mental hook to reuse them elsewhere, which is a different problem than not understanding the paper at all. It’s worth noticing which question trips you up most consistently across papers. If it’s always question 2, the method question, that’s a signal you’re skimming methodology sections and treating them as boilerplate. And the closing list of “things you couldn’t recall” isn’t a failure report, it’s your actual re-reading list, targeted instead of a blind second pass through the whole paper from the top.
Extra Tips 💡
- Run this on a paper you read last month and forgot. It’s a fast way to see how much genuinely stuck versus how much you thought stuck at the time.
- If your guess in step one is way off, don’t rewrite history. Let the AI compare your original guess to the real finding out loud. That gap is the most useful part of the exercise, so don’t skip past it just because it’s a little embarrassing.
- Swap the abstract for just the title if you want a harder version. It forces a rougher first prediction and makes the payoff bigger when you’re proven wrong or right.
- This isn’t chemistry-only. Swap “paper” for any dense source: a technical spec, a long article, a book chapter, even a conference talk transcript.
- Keep a running note of which question number you fail most often. After five or six papers, that pattern tells you more about your reading habits than any single result does.
Re-reading feels productive. It mostly isn’t, because your eyes can slide over familiar text while your brain quietly checks out. Forcing a guess, then forcing a recall, keeps you honest about what you actually know versus what just looks familiar on the page.
Grab both prompts, pick the next paper on your list, and run the two-step before you forget it like you forgot the last one. Head over to the original r/PromptEngineering thread for the full discussion and to see how other researchers are adapting it. ⚓
Frequently Asked Questions
Q: Why does making a guess before reading actually help if I’m going to read the paper anyway?
The guess creates a comparison point, when you discover the actual finding, it contrasts sharply against your prediction instead of getting lost in the stream of information. That friction is what makes it stick in memory. Plus, you actually engage with the abstract instead of skimming it passively.
Q: What do I do if I can’t answer the memory questions after reading?
That’s exactly the signal you need. The prompt lists exactly what you couldn’t recall, so you know the precise sections worth re-reading, way more efficient than reviewing the whole paper. The uncomfortable part is where the learning actually happens.
Q: Does this work for textbooks, or just research papers?
It adapts to anything with clear main ideas. For textbooks, apply it to chapters or key sections instead of full papers. The core mechanism stays the same: predict first, test from memory second.
Q: How is this different from taking notes while reading?
Note-taking feels productive in the moment, but retrieving answers from memory forces much deeper encoding. This prompt saves you the mental overhead of writing questions, so you can focus on the harder work of actually pulling ideas from memory.
Here’s a prompt that turns a paper into a three-question quiz you take from memory after reading
by u/Ok_Layer_1947 in PromptEngineering