great-educators — Feynman, Montessori, Freire

Every craft in the Constellation produces an artifact someone else has to use. Engineers ship code. Designers ship interfaces. Authors ship prose. Each of these artifacts succeeds or fails on whether the next person — the user, the reader, the maintainer — can pick it up and act. great-educators is the craft of making that pickup tractable.

The plugin does not write curricula. It shapes how an artifact is encountered for the first time: what the learner sees on page one, what they can do unaided by the end of section one, what they can verify themselves before they need to ask. It is the craft of designing the path from "never seen this before" to "I just used it correctly."

Why great-educators is a distinct plugin

The failure mode of skipping the educator register is that the artifact technically exists but no one can adopt it. A Skill file is correct and unused. A doc page is accurate and ignored. An onboarding flow covers everything and teaches nothing. The work was done; the handoff failed. The cost of that failure is invisible because it shows up as low adoption rather than a bug report.

A separate great-educators plugin runs a different review than great-authors. The author asks: is this prose clear. The educator asks: can the reader DO something with it after they read it. Two related questions; two different success conditions.

The plugin runs best at three points: when material is being designed (sequence, scaffolding, the order in which difficulty is introduced), when material is being tested (does a real beginner succeed unaided), and when material is being revised (where in the flow did the learner get stuck and why).

The personas

Richard Feynman: explanation from first principles, with the right analogy. The Feynman register strips ceremonial language and finds the physical metaphor that lets a learner see the thing clearly for the first time. A Feynman review asks: where in this explanation am I substituting jargon for understanding, and what is the analogy that would let the reader see the behavior before they meet the equation.

Maria Montessori: developmental scaffolding and self-correcting design. The Montessori register isolates difficulty — one new challenge at a time, structured so the outcome itself reveals correctness. A Montessori review asks: which prerequisite skills am I assuming, and where in the sequence does the learner verify their own progress without needing me.

Paulo Freire: dialogue rather than lecture, lived reality as the starting point. The Freire register treats the learner as a co-investigator, not a recipient. A Freire review asks: am I telling the reader what I want them to know, or am I posing the problem in a way that requires them to think and act, starting from where they actually stand.

What it unlocks

Documentation that converts curiosity into competence. Onboarding flows that produce confident operators rather than passive readers. Skill files whose first sentence orients the learner in their own situation rather than introducing the system's terminology. Lessons that produce a deliverable, not a passive read.

The most valuable use: run a first-pass review of any artifact intended for a beginner — a README, a Skill file, a tutorial — through Montessori before publishing. She will find the prerequisite the artifact assumes but does not name. That single fix accounts for most of the adoption drop-off in technical material.

If you get stuck

If you are not sure which persona to route to, describe what is going wrong. The reader cannot follow the argument: Feynman. The reader cannot complete the task unaided: Montessori. The material does not connect to the reader's actual situation: Freire.

If a piece of teaching is failing all three, the artifact is not the problem — the artifact is too far ahead of the audience. Pull back to the prerequisite the audience actually has, and rebuild from there.

Cross-reference

great-educators is the natural downstream partner of great-authors and the natural upstream partner of great-publishers. The author writes the prose; the educator structures how it is encountered; the publisher decides what container it ships in. When the three handoffs are clean, the artifact converts.

Plugin source

The shipped plugin lives at github.com/sethshoultes/great-minds-constellation/plugins/great-educators. Three educator personas (Feynman the explainer, Montessori the scaffold designer, Freire the dialogic educator). The plugin produces a craft register for instructional design — not certified pedagogy.

Deliverable

Take one piece of writing or documentation you published in the last month that was meant to teach something. Apply the Montessori test: name the prerequisite skill the artifact assumes the reader has. If you cannot name it without re-reading, the artifact assumed it implicitly — which is the most common cause of an artifact that "everyone read and no one used." Write three sentences identifying the assumption and the fix.

Further reading

• "Skills as SOPs" — the longer argument for treating instructional artifacts as factory SOPs: institutional memory fixed in writing, with the order of steps and the verification points specified, so adoption does not depend on the next reader being clever.