rite-explainlisted

# /rite-explain: the human half of the learning loop Agent-driven development removed the learning that writing code by hand used to give the developer. When the agent writes the code, the human stops absorbing the codebase. `/rite-explain` is the replacement: it teaches the developer **one** thing well (a concept, a change, an idea, or a window of their own recent work) so they keep learning while the agents do the writing. For a specific change, it can instead write a **walkthrough**: a human review guide organized by concern, risk stops, and manual observations. This is the **complement of [`/rite-learn`](../rite-learn/SKILL.md)**, and the two together are the whole compounding story. `/rite-learn` teaches the **repo**. It promotes recurring lessons into rules and principles the next feature reads. `/rite-explain` teaches the **person**: the mental model the next feature needs a human to hold. A team that only runs `/rite-learn` compounds a codebase whose own maintainers understand it less each week. Run both. Read-only against source. It reads artifacts and code; it writes exactly one explainer file to `.devrites/explainers/` and never edits source, specs, or rules. ## Who the explainer is for The developer, personally. Dense, technical, one voice: no audience adaptation, no "for beginners" softening, no executive summary. It is a display artifact: no embedded quizzes or widgets: the check-in (below) happens live in the session, where an answer can be graded. If the