Learning Sprint Planner

---
name: learning-sprint-planner
description: Learn any topic in a focused 2–4 week sprint: define a concrete outcome, break it into daily 25-minute sessions mixing input, practice, and recall, with the assistant quizzing you at checkpoints and running a final self-test. Use when someone wants to learn something new fast — a language, a skill, an exam topic.
category: everyday-assistant
---

## Overview

Most self-directed learning fails the same way: an enthusiastic start, a
sprawling shapeless middle, and a quiet fade by week two. A learning sprint
fixes this with constraints — a short timeframe, a concrete outcome, and
small daily sessions instead of heroic weekend efforts. The assistant
becomes your sprint coach and study partner: it helps you define what
"done" looks like, designs the day-by-day plan, mixes up how you study so
you actually retain things, quizzes you at checkpoints, and runs a final
test to prove (to yourself) that it worked. Two to four weeks is long
enough to get genuinely good at something focused, and short enough that
motivation survives to the finish.

## When to use

- You want to learn something specific in the next few weeks —
  conversational Spanish basics, sourdough baking, data analysis, music
  theory, touch typing.
- You are preparing for an exam, interview, or certification and need a
  structured study plan instead of random cramming.
- You have tried learning this before and stalled — you need external
  structure, pacing, and accountability.
- You can commit to about 25 minutes a day but not to multi-hour study
  blocks, and you want a plan that respects that.
- You want to actually retain what you learn, not just consume tutorials
  and forget them by next month.
- You are deciding whether a bigger commitment (a course, a career move) is
  worth it, and want a low-cost sprint to test your interest first.

## Core concepts

- **Outcome before curriculum:** "learn photography" is a wish; "take 10
  manual-mode photos I am proud of" is a sprint. The outcome defines what
  gets studied and — just as important — what gets skipped. The assistant
  pushes you to name something demonstrable, because a demonstrable outcome
  is also your final test.
- **25 minutes beats 0 minutes:** short daily sessions win on consistency,
  and consistency wins on retention. The sprint is designed so a missed day
  is a speed bump, not a derailment — the plan absorbs it without drama.
- **Input, practice, recall — in rotation:** *input* (reading, watching,
  listening) builds familiarity; *practice* (doing exercises, making
  things) builds skill; *recall* (quizzing yourself, explaining aloud)
  builds memory. Input-only learning feels productive and evaporates.
  Every session leans on at least two of the three, and no week is input
  alone.
- **Checkpoints, not just a finish line:** a mid-sprint quiz catches the
  illusion of competence early, when there is still time to fix it. The
  assistant quizzes you conversationally — no test anxiety, just "explain
  X to me" and "what is the difference between Y and Z?" Wrong answers are
  the most useful data in the sprint.
- **Spaced, not crammed:** the plan revisits earlier material in later
  sessions on purpose. Forgetting and re-remembering is the mechanism of
  long-term memory, not a sign of failure — a plan with no revisiting is a
  plan for forgetting.
- **Teach-back as the gold standard:** if you can explain a concept to the
  assistant clearly enough that it "gets it," you know it. The final
  self-test leans heavily on explanation, not multiple choice, because
  recognition is cheap and recall is the real thing.
- **Scope discipline:** a sprint covers one outcome. "Learn Spanish AND
  guitar AND statistics" is three sprints wearing a trench coat. The
  assistant should refuse politely and help you sequence them.

## Practical workflow

The sprint is a conversation from planning through the finish line — you
never stare at a static plan alone.

1. **Define the outcome.** You say: "I want to learn [topic] — help me
   plan a sprint." The assistant asks: What do you want to be able to *do*
   at the end? What do you already know? How many weeks (2–4), and how many
   minutes a day can you honestly give? It then drafts the outcome
   statement and checks it with you: specific, demonstrable, achievable in
   the timeframe. This negotiation is the most important five minutes of
   the sprint.
2. **Build the plan.** The assistant breaks the outcome into weekly
   milestones, then into daily 25-minute sessions, each labeled by type —
   input, practice, or recall — and sequenced so concepts build on each
   other. Earlier sessions get deliberately revisited later for spacing.
   You review the plan and adjust ("I already know the basics, skip week 1"
   / "I want more practice, less reading"). The plan is a draft until you
   approve it.
3. **Run the sessions.** Each day you check in: "Ready for today's
   session." The assistant delivers that day's material or exercise, scaled
   to 25 minutes — a short explanation, a worked example, then you doing
   the thing. Stuck? It explains differently, offers an analogy, or breaks
   the step smaller. Finished early? It offers a stretch task, never filler.
4. **Checkpoint quizzes.** At the end of each week, the assistant quizzes
   you conversationally before unlocking the next week's plan: explain
   concepts back, work through a small problem, spot the deliberate mistake
   in an example. Weak spots get folded into the next week's sessions as
   recall practice — the plan adapts to you instead of marching on
   regardless.
5. **Missed days, handled.** Tell it when life happens: "I missed three
   days." It reshuffles — compressing sessions, dropping the nice-to-haves,
   protecting the outcome — without guilt-tripping. The sprint bends; it
   does not break. What it will not do is pretend you can cram three weeks
   into a weekend.
6. **Final self-test.** In the last session, the assistant runs a
   comprehensive check against your original outcome: perform the skill,
   explain the key concepts, handle a twist you have not seen before. Then
   you both review: what stuck, what needs ongoing practice, and whether a
   follow-up sprint makes sense. End by naming how you will *use* the skill
   in real life within two weeks — use is what converts a sprint into
   lasting ability.

## Common pitfalls

- **A vague outcome.** "Get better at Excel" produces a vague plan and
  vague results. If the outcome is not demonstrable, the sprint has no
  finish line — sharpen it before starting, not midway.
- **All input, no recall.** Watching twelve tutorials feels like learning.
  It is mostly entertainment with educational branding. If a week passes
  with no quiz or practice, the plan is broken — ask the assistant to
  rebalance toward doing.
- **Front-loading too hard.** Starting with two-hour sessions burns out by
  day four, and then the sprint is over before it began. The 25-minute
  default is a feature, not a limitation; increase only after two
  consistent weeks.
- **Skipping checkpoints.** It is tempting to wave off the quiz and keep
  going — it feels faster. The checkpoint is where illusions of competence
  die cheaply; skipping it just moves the reckoning to the final test,
  where it is expensive.
- **Treating a missed day as failure.** One missed day means nothing;
  quitting because of one missed day means everything. The plan explicitly
  absorbs misses — use that instead of restarting from zero in shame, which
  is how most sprints actually die.
- **No next step after the sprint.** Knowledge decays without use, fast.
  End every sprint by scheduling real application within two weeks —
  otherwise plan a lighter "maintenance sprint" of occasional practice, or
  accept the decay honestly.
- **Sprinting on someone else's goal.** If the outcome is something you
  feel you *should* want (your manager's suggestion, a trend), motivation
  will not survive week two. The outcome negotiation in step 1 should
  surface this — pick the sprint *you* want, or do not start it.