oma-explanation

# oma-explanation — Interactive HTML Code-Change Explainer ## Scheduling ### Goal Generate an educational, self-contained interactive HTML document that explains a code change to a reader — deep skippable background for newcomers, core intuition with toy data, a comprehension- ordered code walkthrough, and a five-question quiz — saved under `.agents/results/explain/` and validated against a deterministic checklist. ### Intent signature - User invokes `/explain`, names this skill, or asks for a rich explanation/walkthrough of a diff, PR, branch, or commit range (설명서, 해설, コード解説, 代码讲解). - Another skill or workflow delegates "explain this change as a document" output. - Activation is slash/explicit/delegated only — this skill is intentionally excluded from keyword auto-detection ("explain" is everyday vocabulary; `convert` precedent). ### When to use - Explaining a PR, branch, commit range, or the current staged/unstaged change as a document - Onboarding a teammate onto a change they did not write - Producing a reviewable teaching artifact after a large or subtle change lands ### When NOT to use - Narrated explainer *video* → use `oma-video` (explainer mode); this skill produces HTML documents - Checking whether docs still match the codebase → use `oma-docs` (drift detection) - Presentation deck / slides → use `oma-slide` (fixed 1920×1080 deck contract) - Finding defects or issuing review verdicts → use `oma-qa` (or the `review` workflow); this skill narrates a change ...