PlaybookPrompts

Generate a retrieval-practice problem set from a topic

Education & Learning retrieval-practicespaced-repetitionstudy

Re-reading notes feels productive but produces weak retention. Retrieval practice — recalling information under pressure — is far more effective. This prompt generates a problem set designed around retrieval, not recognition.

Prompt
I have been studying {{TOPIC}} and I want to practice retrieving what I've learned, not just recognizing it when I see it.

Here are my notes or the material I've covered:
{{STUDY_NOTES}}

1. From this material, generate a 15-question retrieval practice set. Use this mix:
   - 5 free-recall questions ("Explain X without looking at your notes")
   - 4 application questions ("Given this scenario, what would you do and why?")
   - 3 comparison questions ("What's the difference between X and Y, and when does the distinction matter?")
   - 2 error-spotting questions ("Here is a flawed piece of reasoning about {{TOPIC}} — identify and correct the error")
   - 1 synthesis question ("Combine at least three ideas from your study material to answer...")
2. Do not include the answers yet. Present the questions only.
3. After I attempt the questions and share my answers, score each one, explain where I was right or wrong, and flag any answer where I was confidently wrong — that is the highest-priority area to revisit.
4. At the end, recommend which 3 questions I should re-attempt in 48 hours based on my performance.

Note: This prompt works best when {{STUDY_NOTES}} is substantive (at least a few paragraphs). If the notes are sparse, the questions will be generic.
Variables to fill in
  • {{TOPIC}}
  • {{STUDY_NOTES}}

How to use this prompt

  1. Copy the prompt above (Copy button on the top-right).
  2. Replace each {{VAR}} with your own value. Variables: {{TOPIC}}{{STUDY_NOTES}}.
  3. Paste it into one of the recommended tools below.
  4. 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.

Heads up: some of the links on this page are affiliate links — meaning we may earn a commission if you sign up after clicking, at no extra cost to you. We only recommend tools we'd put on our own stack. You can see our full affiliate disclosure here.

Pair this prompt with a tool

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.