Once the task manager question was settled, I could focus on what the vault actually needed to contain.

The goal was simple: every Docker and Kubernetes lesson should have a home in the vault before I watch it, a note created during it, and a review scheduled after it. No manual steps, no decisions to make in the moment.

The Learning Plan Structure

The Udemy course has 26 lessons spread across Docker and Kubernetes. I mapped them to a 5-week calendar: two sessions per day this week at 09:30 and 11:00, then one session per day at 06:35 from June onwards when I shift to an earlier schedule.

Each lesson gets a pre-built file in projects/DevOps Learning/_Learning Plan/. The file contains the lesson title, the list of individual Udemy videos with durations, and three questions generated in advance from the lesson content. The questions are there before I start — not to answer immediately, but to prime the learning. What am I looking for in this lesson?

# 🐳 Lesson 4 — Networking: Container Communication

Date: 2026-05-27
Session: AM1 (09:30)
Duration: 51 min
Videos: 67–78

## Sub-lessons

- [ ] 67. Case 1: Container to WWW Communication (4min)
- [ ] 68. Case 2: Container to Local Host Machine (2min)
...

> [!info] ### Questions
> 1. How can a container communicate with the host machine?
> 2. How do two containers on the same Docker network communicate?
> 3. Why use container names instead of IP addresses?

Tick off videos as you watch them. The questions sit there as a reminder of what to pay attention to.

After the Lesson

After the session, a separate note gets created from a Templater template — the session note. This is where the reflection goes: what I actually learned in my own words, the WHY (why does this matter for real DevOps work?), key concepts, anything that confused me tagged with #revisit.

The session note gets a difficulty rating at the bottom: #easy, #medium, or #hard. That rating drives the spaced repetition schedule.

Spaced Repetition

Running /lesson-review in Claude Code reads the session note, finds the rating tag, and schedules review sessions into future Quiz & Review calendar events:

  • Easy: +7 days, +21 days
  • Medium: +3, +7, +21 days
  • Hard: +1, +3, +7, +21 days

The review questions from the original lesson appear inside the yellow Quiz & Review calendar event on those future dates. Past questions stack below today’s questions — one event, multiple lessons worth of review material.

Reclaim sees those calendar events and schedules around them automatically.

The Lessons Index

With 26 lessons mapped to specific dates, I needed one place to see the whole picture. _Learning Plan/Lessons Index.md is a simple table — lesson number, date, title, videos, duration, status. When a Claude Code skill needs to find a lesson file, it reads this table directly. No searching.

The status column goes from ⬜ to ✅ as lessons complete. At any moment I can open this file and see exactly where I am in the course.

Next: the skills that make the morning routine actually work — and why the morning briefing took three rebuilds to get right.