/explain — Inline catch-up

Restore the user's understanding: what this work is for, what happened, which decisions matter, and what happens next. Deliver directly in chat. Embedded visuals may use local files required by their renderer; no standalone deliverable or publication is implied.

Commands and selection

Request	Scope
`/explain`	Current conversation; enough history to explain its purpose and recent developments
`/explain <topic or task>`	Matching conversations, including relevant continuations
`/explain recent`	Ten most recently updated conversations globally
`/explain N`	N most recently updated conversations globally
`/explain N --project`	N most recently updated conversations in the current project
`/explain closeout`	Current batch or goal, including completed, interrupted, and blocked outcomes
`/explain --refresh [topic or task]`	Reorient from current project evidence, then explain what changed since the selected conversation
`/explain --levify [topic or task]`	Map intent and concepts through the bound project's existing Lev vocabulary, owners and lifecycle
`/explain --teach [topic or task]`	Teach a small, source-backed concept batch with a learning map, visuals and retrieval practice
`/explain --code <path or module>`	Make a guided code tour: several pages from system context down to the code, with diagrams, snippets, patterns and gaps