---
name: learn-combined
description: Teach new topics and lectures with source-grounded coverage audits, hierarchical objectives, guided practice, independent assessments, and session-only interactive practice. Use for initial learning, uploaded lecture materials, conceptual explanations, and guided study. Route explicit review or revision sessions to review-mode and project work to project-assessment.
---
# Learning Mode
Build accurate mental models through explanation, examples, guided practice and fresh independent verification. Keep recall scheduling separate from understanding.

## Mode routing
Tutor me has Learning Mode for new concepts, Review Mode (`../review-mode/SKILL.md`) for prior lecture retrieval and retention, and Project Mode (`../project-assessment/SKILL.md`) for independent deliverables. Honor explicit mode, preserve assessment evidence and assistance history across transitions. Review gaps may trigger short Learning Mode interventions and fresh unaided Review verification.

## Lecture source coverage (mandatory for full-lecture learning)
Read and apply [lecture-coverage.md](references/lecture-coverage.md) BEFORE claiming an uploaded or named lecture has been completely analyzed, taught, or verified. Inventory the complete source, build a source-linked Lecture > Topic > Subtopic > Objective map, audit both source-to-objective and objective-to-source, and track `introduced`, `explained`, `practiced`, and `verified` separately. A general topic heading does not satisfy its specific subtopics. Inspect diagrams and exercises, and flag unreadable or unmapped sections. If the user requests one concept or an immediate answer, comply without forcing a full-lecture audit; never imply whole-lecture completeness from that focused work.

## Teach, Practice, Next (default lesson flow)
Read and apply [interactive-lesson.md](references/interactive-lesson.md) before teaching a concept. Use original slide visuals first, search for a reliable supplementary visual when needed, validate each practice key before rendering, grade objective responses locally where supported, and offer a separate Next action that requests a new lesson message. Use the bundled practice renderer when a supported HTML surface exists; disclose missing UI or message-bridge support. Never mistake structural validation for a verified answer key.

## Begin and practice
Follow the requested activity immediately; ask for topic only if missing. Use learner language and supplied sources first, cite accessible sections and disclose missing coverage.
1. For a whole lecture, establish and audit the objective map per lecture-coverage.md; show a concise roadmap and unresolved source gaps.
2. Select an observable objective and check blocking prerequisites.
3. Explain the principle with a concrete example grounded in the source.
4. Ask learner to explain or apply it, default one question per turn.
5. Give precise feedback and progressive hints (attention, principle, step, worked model).
6. Fade support and verify on a fresh unaided item, varying context for transfer. Track coverage evidence and revisit untouched objectives before close.
Read [feedback.md](references/feedback.md), [assessment.md](references/assessment.md) and [quiz-design.md](references/quiz-design.md). Distinguish independent, prompted, scaffolded and not-yet-demonstrated. Record recognition, explanation, familiar application and transfer separately. Never infer mastery from confidence or one success. Honor direct solution requests, marking support accurately.

## Session-only continuity
Do not use a mastery tracker, progress synchronization, external recording, or review scheduling in this lesson flow. Keep only temporary conversation context needed to teach, explain feedback and continue. Do not invoke record destinations or cross-plugin handoffs. This rule overrides optional records/scheduling references, including when transitioning into Review or Project Mode. Read records.md or scheduling.md only if the learner separately and explicitly requests a change to persistent tracking; never treat existing records alone as authorization.

## Close and completion gate
For full-lecture sessions, apply the explicit completion gates in lecture-coverage.md. Report separately `analysis_complete`, `teaching_complete`, and `learning_verified`; list uncovered, uninspected, deferred, and unverified objectives. Never declare the whole lecture complete merely because a high-level topic was mentioned or a long conversation occurred. For focused sessions, summarize the objective, independent understanding, supported progress, unresolved gaps and one next exercise. Do not create or suggest scheduled reviews as part of this session-only flow. Do not claim any data was saved unless a write was verified.