PlaybookPrompts

Pre-mortem a learning plan before you start it

Education & Learning planningself-studyaccountability

Most self-study plans fail not because the content is wrong but because the plan ignores real constraints — your schedule, motivation patterns, and what happens when work gets busy. This prompt stress-tests a learning plan before you invest time in it.

Prompt
I have a learning plan I want to pressure-test before I commit to it. Here is the plan:
{{LEARNING_PLAN}}

My constraints and context:
- Available time per week: {{HOURS_PER_WEEK}} hours
- Deadline or target date: {{TARGET_DATE}}
- My biggest historical obstacle when self-studying: {{PAST_OBSTACLE}}

1. Evaluate whether the plan is realistic given my time constraints. Calculate whether the content volume fits into {{HOURS_PER_WEEK}} hours per week by {{TARGET_DATE}}, and flag if there's a gap.
2. Run a pre-mortem: imagine it's {{TARGET_DATE}} and I did not complete the plan. Generate the 5 most likely reasons this happened, ranked by probability given the context I've shared.
3. For each failure reason, suggest a specific structural change to the plan that would reduce that risk. Be concrete — don't suggest "stay motivated," suggest a specific schedule change, accountability mechanism, or scope reduction.
4. Identify the one weakest point in the plan — the stage or week most likely to cause abandonment — and redesign that section.
5. Produce a revised version of the plan with your recommendations incorporated.

Note: If {{LEARNING_PLAN}} is very high-level (e.g., just a topic list), ask me to flesh it out with weekly milestones before proceeding with the pre-mortem.
Variables to fill in
  • {{LEARNING_PLAN}}
  • {{HOURS_PER_WEEK}}
  • {{TARGET_DATE}}
  • {{PAST_OBSTACLE}}

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: {{LEARNING_PLAN}}{{HOURS_PER_WEEK}}{{TARGET_DATE}}{{PAST_OBSTACLE}}.
  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.