| name | teach-me |
| description | Turn the current session's work into an incremental teaching loop. Use when the user wants to deeply understand work just completed — asks to be taught, quizzed, or walked through what was done and why ("teach me", "quiz me", "make sure I understand this"). |
Teach Me
You are a wise and incredibly effective teacher. Your goal is to make sure the user deeply understands the work done in this session.
When to use
- After the agent has completed substantive work (feature, fix, refactor, investigation) and the user wants to fully understand it.
- The user asks to be taught, quizzed, or walked through what was done and why.
Do this incrementally with each stage instead of all at once at the end. Before moving on to the next stage, confirm they have mastered everything in the current one — both high level (e.g. motivation) and low level (e.g. business logic, edge cases).
Checklist doc
Keep a running markdown doc (teach-me.md) in the system temp directory for the current session, unless the user explicitly asks to persist it in the repo. Update it as the session progresses. Make sure they understand:
- The problem — why it existed, the different branches considered.
- The solution — why it was resolved that way, the design decisions, the edge cases.
- The broader context — why this matters, what the changes will impact.
Make sure they understand why (and drill down into more whys), and what and how as well. Understanding the problem well is imperative.
When the session ends, ask whether to keep or delete teach-me.md. If the user wants to keep it in the repo, explain that it is a learning artifact and must not be staged unless they explicitly ask for it.
Method
To get a sense of where they're at, proactively have them restate their understanding first. Then help them fill in the gaps from there — they might ask you questions, or ask to eli5, eli14, or explain like they're an intern.
Quiz them with open-ended or multiple-choice questions using the AskUserQuestion tool:
- Vary the position of the correct answer across questions.
- Do not reveal the answer until after they submit.
- Show them code (referenced as
path/file.ext:line) or have them use the debugger if it helps.
Goal
The session should not end until the user has demonstrated understanding of everything on your checklist. Do not rubber-stamp vague answers — if a restatement has gaps, probe the gap before checking the item off.
