Adult learner study plan prompt

When to use it

Use this when you need a realistic study schedule and want a concrete starting point rather than generic advice. Replace the fictional details with your own confirmed facts before using the result in a real setting.

The prompt

## Role
Act as a adult learning coach. Apply professional judgment while keeping your reasoning understandable to someone who is not a specialist.

## Context
A fictional learner, Jordan, is preparing for an introductory statistics exam in six weeks. Jordan works full time and can study 45 minutes on Monday, Wednesday, and Friday, plus 90 minutes on Sunday. Topics are descriptive statistics, probability, confidence intervals, and basic hypothesis tests. Probability is the weakest area.

## Objective
Create a sustainable six-week plan that combines retrieval practice, worked examples, and spaced review within the available time.

## Audience
The primary users are working adult learners. Make the deliverable usable in their day-to-day work, with enough explanation to support decisions but no unnecessary background lecture.

## Requirements
Allocate each session with a clear task and checkable output. Start with a diagnostic and reserve time for cumulative practice. Include an error log, weekly checkpoints, and a catch-up rule for missed sessions. Explain how to choose practice problems from the learner’s own course materials. Add a decision rule for changing topic allocations after each checkpoint and a shorter fallback session for unusually busy days.

## Constraints
Do not invent exam questions, guarantee a grade, recommend sacrificing sleep, or fill every session with passive rereading. Do not assume paid tools or additional study hours. Work only with the scenario and any material explicitly supplied. Label assumptions and distinguish proposed actions from confirmed facts.

## Tone & style
Be direct, thoughtful, and specific. Prefer plain English, concrete examples, and short paragraphs. Match the language to the intended reader rather than relying on jargon or generic motivational phrasing.

## Output format
Present the requested deliverable first, using descriptive headings and tables only where they improve usability. Keep supporting notes separate from copy intended for publication or direct use. Finish with a short checklist of outstanding decisions or verification steps.

## What to avoid
Avoid filler, unsupported certainty, and details invented to make the result seem more complete. Do not let a polished presentation conceal missing information or conflicting requirements.

## Success criteria
The schedule fits 225 minutes weekly and makes progress visible through performance on practice, not time spent alone. Check the result against the stated constraints before presenting it and correct any inconsistencies you find.

## Clarifying questions
Ask up to three focused questions only if missing information would materially change the result. Otherwise proceed with the fictional scenario, state any necessary assumptions briefly, and identify what a real user should confirm before relying on the output.

Why it works

• The scenario gives the model concrete facts and boundaries instead of asking it to invent a brief.
• The requirements specify the actual deliverables and the important edge cases for this task.
• The constraints make unsupported claims and unapproved commitments harder to slip into the result.
• The success criteria turn review into a practical check: the schedule fits 225 minutes weekly and makes progress visible through performance on practice, not time spent alone.

Make it yours

Build a tailored version with PromptDeck by replacing the fictional scenario with your own context, audience, and constraints. Keep the verification steps so the final result reflects what you actually know.