Re-Teach Tomorrow
“They missed it today? Here's a fresh set for tomorrow.”
Illustrative team — open seats are real invitations.
- Build mode
- assemble on blocks
- Built on
- @k12vls/worksheet-core + @k12vls/marp-slides (+ optional @k12vls/slides-to-video)
- Output
- remediation worksheet + short explainer (slides or video)
The brief
What it is, and why a teacher says yes
The pain point
A class misses a skill, and the teacher has to build fresh remediation overnight — new practice and a new way to re-teach it — on top of everything else. It's recurring, it's tonight, and it's the moment good intentions die from lack of time.
What it does
Teacher names the standard students struggled with → gets a remediation worksheet aligned to that skill and a 2-minute explainer on the same skill (a slide deck, or a short video rendered from it). Practice plus re-teaching, in one step.
Why it's adoptable
It targets a moment of real, dated need — “they didn't get it today” — and it pairs the two things a teacher would otherwise assemble separately (practice + re-teaching) into a single generate. The teacher reaches for it because tomorrow is already a problem.
What the teacher receives — a synthetic example
Multiplying Fractions — Re-Teach
- Shade the area model for 1/2 × 6.
- Is 1/2 × 6 larger or smaller than 6? Why?
… ~5 more problems …
- 1What “1/2 of 6” means
- 2The area model, drawn
- 3Why the answer is smaller
- 4One you try
Slides by default; video is the optional home-viewing path.
Illustrative mockup. All example data is synthetic — no real student data.
The graduation signal
“Built” doesn't count — real, repeated use does. Here's the ladder.
- 1
Pilot
The teacher reaches for it the first time a skill slips and gets a usable remediation set plus explainer out of it (teacher-side).
- 2
Active use
The teacher returns to it whenever a skill slips — repeat use tied to the real “they didn't get it” moments, correlating with assessment dips (teacher-side); where the explainer goes home, students served with it — teacher-confirmed or estimated from the class, not raw watch telemetry (student-side).
- 3
Sustained MAU
Teacher-side MAU — repeat use that holds across a term, with student participants counted separately, not as logins, and estimated from classes served; where the explainer is assigned for home viewing, the artifact may also add a steady student-side MAU on the explainer (student-side).
For the AI Builder
How you build it
The honest build path — what it builds on, the rough assembly, the data flow, and the gaps the blocks don't give you for free.
Blocks it builds on
- @k12vls/worksheet-core — the remediation worksheet half: the CCSS standards model, problem-generation config + record types (CcssProblemGenerationConfig, CcssProblemRecord), the problem-gen prompt constants (getProblemGenSystemPrompt), rendering UI (@k12vls/worksheet-core/ui), and PrintOptions + print styles.
- @k12vls/marp-slides — the explainer half (lighter path): a shipped package that produces Marp decks, exporting its types plus a K12 theme (K12_THEME_NAME, k12ThemeCSS, writeK12ThemeFile). The 2-minute explainer is authored as a Marp deck on the one skill.
- @k12vls/slides-to-video (optional, heavier path) — a shipped package exporting generateVideo, which turns the deck into a short MP4. Use this only when the teacher wants a video the class can watch at home.
Rough assembly
- 1Pick — a standard selector populated from the worksheet-core CCSS standards tree; the teacher names the skill that didn't land, plus a practice-length input wired to numProblems on the config (a quick warm-up set vs. a full re-teach packet).
- 2Generate practice — call the LLM with getProblemGenSystemPrompt(...) + a CcssProblemGenerationConfig to produce remediation problems (and answers) as CcssProblemRecords.
- 3Render worksheet — display worksheet + answer key with the worksheet-core ui components; apply PrintOptions for print/PDF.
- 4Generate explainer (slides) — author a short Marp deck on the same standard (a focused LLM call), styled with the marp-slides K12 theme (writeK12ThemeFile / k12ThemeCSS). This is the default, lighter output.
- 5Optional — render to video — if the teacher wants a home-viewing clip, pass the deck to generateVideo from slides-to-video to produce a short MP4. (See caveat: heavier.)
The data flow
CcssProblemGenerationConfig.getProblemGenSystemPrompt.CcssProblemRecord).worksheet-core/ui; apply PrintOptions (worksheet · key).marp-slides K12 theme.generateVideo (slides-to-video) → a short MP4 explainer.Caveats — the honest gaps
Scope boundaries
This generates a remediation set and a view-only explainer — it is not an LMS: it does not track who watched, collect student work, or record scores, and the moment it starts saving sessions or capturing input it stops being a no-data print/view tool and crosses into the safeguarding load it was scoped to avoid.
For the AI Champion
Taking it to a teacher
The adoption kit — the pitch, the pain it lands on, the objections you'll hear, and what a real pilot looks like.
The 30-second pitch
“Class didn't get today's skill? Name the standard, and this hands you a fresh remediation set for tomorrow plus a 2-minute explainer on exactly that skill — slides you can show, or a short video you can send home. You don't have to build either one tonight.”
The pain it lands on
The overnight rebuild — a class missed a skill, and now the teacher owes both new practice and a new way to explain it by first period tomorrow.
Objections → responses
“Is the practice really on the skill they missed?”
It's generated from the exact Common Core standard you name, so both the worksheet and the explainer target that one skill.
“I don't have time to make a video.”
You don't. The default is a ready-to-show slide deck; the video is one optional extra step, only if you want something to send home.
“Where does my students' data go?”
Nowhere. It generates a worksheet and an explainer; no student logs in and no student data is stored (the worksheet and explainer are yours to keep, like any lesson material). If you assign the explainer for home viewing, students just watch — there's still no account and no data collected.
What a pilot looks like
The teacher uses it the next time a skill slips, then again the time after that. Success = repeat use tied to the real “they didn't get it” moments — and, where the explainer goes home, the teacher confirming students were served with it (the program counts students served, not watch telemetry — there is none).
The bar
Safeguarding & the pilot gate
The minimum conditions before any classroom use, and the data posture that keeps the solution honest.
Pilot gate
- Sponsoring adult
- The classroom teacher (required program-wide) — or, where the venue is a school, after-school program, or community setting, the sponsoring adult who serves the real learners there.
- Minimum version
- Name a standard → a real remediation worksheet + answer key on that skill, plus a 2-minute explainer slide deck on the same standard. The video path is optional and not required to pilot.
- Pilot setting
- The teacher's own class — the worksheet printed for tomorrow's practice and the explainer shown in class (and, if wanted, the video sent home).
- Success evidence
- The teacher reaches for it the first time a skill slips and gets a usable remediation set plus explainer out of it; where the explainer goes home, the teacher confirms students were served with it (teacher-observed or estimated — there is no view tracking).
- Stop condition
- Immediate — the teacher reviews the generated worksheet/explainer and judges it not usable for tomorrow (off-standard, off-grade, or thin), so it doesn't get used at all; or, over the pilot — the practice/explainer didn't land on the skill, or the teacher doesn't return to it the next time a skill slips, i.e. it missed the overnight-rebuild moment.
Safeguarding
Low–med loadData touched
No student data — the teacher-selected CCSS standard generates the worksheet and the explainer (and passes through the LLM generation calls); when assigned home, a student watches the explainer (view-only). No student login, no PII, no uploads, no completed work. No student data is persisted; the worksheet and the explainer (deck/video) are ordinary lesson material the teacher may save, reprint, or re-share, holding no student data.
Checklist
- Sponsoring teacher ✓ (required program-wide).
- Data-handling review n/a (no data collected).
- Consent n/a.
- Supervision = the teacher owns whatever they assign for home viewing.
- Content review applicable — the remediation set and the explainer (slides/video) are LLM-generated and reach students, so the sponsoring teacher verifies correctness, standard alignment, and suitability before assigning or sending home (a required classroom quality/safeguarding gate, not a data-handling item).
One thing to verify
That the generated explainer (deck or video) contains only the math — no links, prompts, or affordances that would pull a student off-platform or invite input — so “view-only, no data” holds for the home-viewing case in practice, not just intent.
What would change the load
The current “no data collected, view-only” profile holds only as long as the explainer stays consume-only and generation/printing stays off the firebase-auth login path. Adding any of — a student login, telemetry on who watched the explainer, student uploads or saved work, a submission/response affordance on the explainer, parent contact, or personalized feedback — turns the home-viewing artifact into a data-collecting surface and pushes the load above Low–med. Until one of those is added, the profile above stands.
Want to build Re-Teach Tomorrow?
Tell us this starter caught your eye — or browse the others first.