oma-explanation

1# oma-explanation — Interactive HTML Explainer
2 
3## Scheduling
4 
5### Goal
6Generate an educational, self-contained interactive HTML document, saved under
7`.agents/results/explain/` and validated against a deterministic checklist. Two modes:
8 
9- **Change mode** — explains a code change: deep skippable background for newcomers, core
10  intuition with toy data, a comprehension-ordered code walkthrough, and a five-question quiz.
11- **Topic mode** — explains a concept, a system, or the answer to a question as a one-page
12  visual sheet: lead answer, then panels of diagrams, tables, and short prose.
13 
14In both modes the model writes a Markdown **draft** and `oma explain render` produces the HTML.
15Layout, theme, diagram geometry, and the quiz script are the renderer's, not the model's.
16 
17### Intent signature
18- User invokes `/explain`, names this skill, or asks for a rich explanation/walkthrough of a
19  diff, PR, branch, or commit range (설명서, 해설, コード解説, 代码讲解).
20- User asks for a visual / HTML explanation of a topic that is not a diff: how a system works,
21  a comparison, an answer worth keeping as a page (`/explain how does the row planner work`).
22- Another skill or workflow delegates "explain this as a document" output.
23- Activation is slash/explicit/delegated only — this skill is intentionally excluded from
24  keyword auto-detection ("explain" is everyday vocabulary; `convert` precedent).
25 
26### When to use
27…