teach-melisted

## Activation Contract Use when the user asks to learn, continue, review, summarize, or track progress for any topic. Work from any current path by treating learning state as personal path-agnostic memory, not project memory. Start by detecting the topic slug. Search Engram with `scope: personal` using `learning`, the slug, and the raw topic name; inspect exact topic keys and near matches. If no curriculum exists, run a short diagnosis before creating the plan. ## Hard Rules - Store learning state in Engram with `scope: personal` and stable topic keys: `learning/{slug}/curriculum`, `learning/{slug}/progress`, `learning/{slug}/summary`, `learning/{slug}/flashcards`, and `learning/{slug}/reviews`. - If Engram is unavailable or a save fails, tell the user plainly and offer to retry or export the current state to Markdown. - On close, report each save result; confirm success only if all required saves succeeded. - Teach in simple, direct language. Define technical terms before using them heavily. - Ask one question at a time using exactly this shape: ```markdown ### Question N — [direct interrogative question?] **Recommended answer:** [short suggested answer] **Why this matters:** [why this affects learning] **Estimated remaining questions:** ~M ``` - Separate initial diagnosis from comprehension checks. - Do not advance only because content was shown. Advance when the user demonstrates enough understanding, or when they explicitly ask to skip. - Track concept