teach

The user has asked you to teach them something. This is a stateful request - they intend to learn the topic over multiple sessions.

Teaching Workspace

Treat the current directory as a teaching workspace. The state of their learning is captured in this directory in several files:

• MISSION.md: A document capturing the reason the user is interested in the topic. This should be used to ground all teaching. Use the format in references/MISSION-FORMAT.md.
• UNDERSTANDING-MAP.md: A structured snapshot of what the learner currently understands. Produced by the Probe phase. Each sub-topic is marked mastered / partial / unknown. Updated (overwritten, not appended) after each Probe. This is the primary input to Plan and the basis for zone of proximal development.
• PLAN.md: A dependency graph of what to learn, in what order. Nodes are concepts; edges are prerequisites. The frontier (currently-learnable nodes, prerequisites met) and fog (sensed but not yet specifiable) are marked. Small topics use a Mermaid graph in this file; large topics that span sessions escalate to a wayfinder map on the issue tracker.
• ./lessons/*.html: A directory of lessons. A lesson is a single, self-contained HTML output that teaches one tightly-scoped thing tied to the mission. This is the primary unit of teaching in this workspace.
• ./session-log/*.md: A directory of session logs. Each interactive teaching session appends one file (0001-YYYYMMDD.md) recording what was probed, what was taught, quiz results, and learner feedback. This is the raw flow that Plan reads to decide what to teach next and when to stop. It is distinct from learning-records — logs are the stream, records are the distillation.
• ./reference/*.html: A directory of reference materials. These are the compressed learnings from the lessons - cheat sheets, reference algorithms, syntax, yoga poses, glossaries. They are the raw units of learning. They should be beautiful documents which print out well, and are designed for quick reference.
• RESOURCES.md: The single interface into the knowledge base. Knowledge entries point into OKB (the open-knowledge-base) — gold/ notes when available, silver/ otherwise. Wisdom entries keep community links. Use the format in references/RESOURCES-FORMAT.md.
• ./learning-records/*.md: A directory of learning records, which capture what the user has learned. These are loosely equivalent to architectural decision records in software development - they capture non-obvious lessons and key insights that may need to be revised later, or drive future sessions. They are titled 0001-<dash-case-name>.md, where the number increments each time. Use the format in references/LEARNING-RECORD-FORMAT.md.
• ./assets/*: Reusable components shared across lessons. See Assets.
• GLOSSARY.md: Subject-term definitions accumulated across lessons (teaching-loop terms live in the skill's CONTEXT.md instead). Use the format in references/GLOSSARY-FORMAT.md; learning-records link here instead of duplicating term definitions.
• NOTES.md: A scratchpad for you to jot down user preferences, or working notes.

The Teaching Loop: Probe → Plan → Teach