Course Plan & Operating Manual · Living Document
An interest-driven 8th grade writing curriculum, built at home, taught one nameable technique at a time.
This document is the course. It defines the year's goals, the quarter-by-quarter map with due dates, and — most importantly — the protocols used to run it day to day: how each daily handout gets generated, how completed work gets evaluated, and how the course gets steered as we learn what's working. Individual lessons are not pre-written; they are created each morning from the recipe in §6, aimed at whatever the skills tracker (§5) says matters right now. That is by design: the research says responsive teaching beats a fixed script, and it keeps the course steerable all year.
writing/completed/. Run the evaluation protocol in §7 — conference, then feedback note — and update the skills tracker.Standing rule for every lesson, all year: each lesson teaches one nameable technique, shows it working in a mentor text, then has her use it immediately with a specific product goal. Assigning writing is not teaching writing. If a handout doesn't have a technique you can name in five words, it isn't ready to print.
By the end of May 2027, the student will have:
The same shape every school week, all four quarters. Content changes; the rhythm doesn't.
| Cadence | Activity | Notes |
|---|---|---|
| Daily · 10 min minimum | Freewrite / journal | Low stakes, never graded, never corrected. Stream-of-consciousness, any topic, no rules; turned in with the day's work. Prompt optional — her choice always wins. On every handout. |
| Daily · 10 min minimum | Sentence drill | One Hochman-style exercise — combine, expand, because/but/so, subordinate opener — built from whatever she's currently reading or writing. This is where comma splices actually get fixed. Included as the warm-up on every handout. |
| 2–3×/week | Lesson + assignment | A printed handout (§6): one technique, one mentor text, one assignment with specific product goals. Numbered continuously; STATUS.md tracks the next number. Never just read aloud — the technique gets modeled live first (§6): you try it in front of her before she uses it. |
| 1–2×/week | Write together | Inside the lesson or drafting block: co-draft an opening, trade alternating paragraphs, or both write to the same prompt and compare drafts. Collaborative writing is one of the research's strongest elements, and in a class of one, you are the partner. |
| Daily · 40–60 min | Drafting | The non-negotiable heart of the day. Significant writing toward the current piece, every school day — the Challenge dial in STATUS.md sets the floor (currently 400+ words). Volume with enjoyment is the whole game; skill follows volume. Drafting happens on a word processor: she writes in Google Docs and sends the doc when finished; you print it for her hands and send a copy back in chat, so every piece exists both ways (the evidence review's word-processing findings endorse exactly this). And some days each week, write alongside her — your own notebook, your own project, visible struggle included. The mentor who writes is the practitioner canon's deepest rule. |
| Most Fridays | Ship | A week of daily writing usually leaves something worth finishing and sharing — read aloud at dinner, printed, mailed. Scale flexes: a complete short piece (500–1,000 words), an installment of a cumulative project, or a capstone stage delivered as a real thing. A celebration, not a deadline: if the piece needs another week, it takes it. What never slides is the daily writing. |
| Weekly · 15–20 min | Conference | Usually paired with the Friday ship: a short, real conversation about the week's piece. She talks first — what was she trying to do, where did it fight her. You answer as a reader ("here's where I leaned in; here's where I got lost"), then one named strength, one teaching point, and agree the next piece's goal together. The §7 feedback note is this conversation's written record, not a replacement for it. |
| Quarterly | Review + steer | Re-read the quarter's work together, write the growth memo (§7), adjust the next quarter's plan (§8). |
Four quarters, each anchored in one mode, sequenced to start where her enthusiasm already is. Dates follow the school calendar; due dates are the fixed milestones. Weekly technique order within a quarter is a menu, not a schedule — pick based on the tracker and what her current piece needs. The Friday ship rhythm (§3) runs all year: the Q1 table below maps every ship — targets, not tests; only capstone dates are fixed. Q2–Q4 tables name the anchor milestones only, and what the in-between Fridays ship gets decided at each quarterly review.
| Quarter | Dates | Anchor mode | Capstone deliverable | Capstone due |
|---|---|---|---|---|
| Q1 | Aug 3 – Oct 2 | Narrative & description | Original short story, published | Fri Oct 2 |
| Q2 | Oct 19 – Dec 22 | Informative / explanatory | Research report, formatted & published | Fri Dec 18 |
| Q3 | Jan 5 – Mar 12 | Argument | Full argument essay with counterclaim | Fri Mar 12 |
| Q4 | Mar 29 – May 28 | Capstone / multi-genre | Her chosen capstone + year portfolio | Fri May 21 |
Breaks: Labor Day Sep 7 · Fall Break Oct 5–16 · Thanksgiving Nov 25–27 · Winter Break Dec 23–Jan 4 · MLK Jan 18 and Presidents' Day Feb 15 (unless used for make-up) · Spring Break Mar 15–26. No milestones land adjacent to a break re-entry; first week back is always a soft week.
The point of this quarter: she already writes complete stories with real arcs and revises voluntarily. Q1 sharpens the craft inside that enthusiasm: dramatizing instead of naming emotion, varying sentences, handling dialogue mechanics, and building real paragraphs — while establishing the daily rhythm and the feedback culture.
This quarter's named strategy: her story planner, made official. She already plans before drafting; together, turn those instinctive moves into a named, written strategy (character + want + obstacle + turn + ending — her real moves, her name for it), model planning a fresh story aloud with it, then hand it over. It's hers when she runs it unprompted on a new piece — advance by criterion, not calendar (§6).
| Ships | Scale | Friday |
|---|---|---|
| Lessons 1–4 (snapshot, dragon story, creature study, dialogue scene) — done, evaluated | — | ✓ |
| Piece 2: HTTYD scene rewritten from another character's POV, or "The Dragon in the Mist" revisited applying show-don't-tell + dialogue mechanics | Full piece — shared at home | Fri Aug 14 |
| Field guide entry #1 — one illustrated creature entry (description muscle: precise nouns, sensory detail) | Installment | Fri Aug 21 |
| Field guide entry #2 | Installment | Fri Aug 28 |
| Piece 3: Creature field guide assembled — 3+ illustrated entries, titled and bound/printed | Full piece — shared | Fri Sep 4 |
| Capstone stage 1: original short story in her own world (not a continuation) — planned, and the opening scene read aloud | Capstone stage | Fri Sep 11 |
| Capstone stage 2: full draft delivered | Capstone stage | Fri Sep 18 |
| Capstone stage 3: revised with feedback | Capstone stage | Fri Sep 25 |
| Q1 Capstone: the story published — printed and read aloud, or mailed | Full process + publication | Fri Oct 2 |
These Fridays are targets, not tests — only the capstone date is fixed. If a week wobbles, shrink that Friday's ship (§8: shrink the piece, not the process) or let it slide a week; what never slides is the daily writing. Labor Day Sep 7 shortens the stage-1 week to four days — planning week, so it absorbs it. Fall Break Oct 5–16 follows the capstone, so the quarter ends on a celebration, not a scramble.
The point of this quarter: writing that teaches a reader something, using more than one source. Summarization (tied for the research's strongest practice) lives here. The trick is keeping it interest-driven: ferrets, insects, Minecraft, and how animation works are all legitimate research topics.
This quarter's named strategy: the summarizing rule set — keep the main idea, delete the trivial and the redundant, write the synopsis in your own words. Modeled on real sources, practiced weekly, handed over; it powers the note-taking and quoting work on the menu below.
| Deliverable | Full process? | Due |
|---|---|---|
| Research topic chosen + 3 candidate sources found | — | Fri Oct 23 |
| Piece 1: a short explainer or how-to in her wheelhouse (Minecraft guide, "how animation works," pet-care how-to) with headings and one diagram | Yes — shared | Fri Nov 13 |
| Research report: notes + outline complete | — | Fri Nov 20 |
| Research report: full draft (Thanksgiving Nov 25–27 falls after) | — | Fri Dec 4 |
| Q2 Capstone: research report revised, formatted, published (printed booklet or shared digitally with family) | Yes — full process + publication | Fri Dec 18 |
| Dec 21–22: read-aloud, wrap-up, no new work | — | Dec 22 |
The point of this quarter: the 8th grade summit — state a claim, support it with evidence, and take the other side seriously enough to answer it. Start with arguments she has actual stakes in; formality comes last.
This quarter's named strategy: TREE, plus the counterclaim move — Topic (the claim), Reasons (three or more), Explain each, Ending; then "someone might say… but…" planned in from the start, not bolted on. Modeled first on an argument she has real stakes in, then run on every argument piece until she plans with it unprompted.
| Deliverable | Full process? | Due |
|---|---|---|
| Piece 1: a review with a defended ranking (e.g. "the best HTTYD film," best Minecraft update, best book this year) — evidence from the works themselves | Yes — shared | Fri Jan 29 |
| Piece 2: a real persuasive pitch — something she actually wants (a pet, a trip, a purchase, a privilege), delivered to its real audience (us), and answered seriously | Yes — delivered | Fri Feb 19 |
| Argument essay: claim chosen + evidence gathered (e.g. "animals X should/shouldn't be kept as pets") | — | Fri Feb 26 |
| Argument essay: full draft | — | Fri Mar 5 |
| Q3 Capstone: argument essay revised and finished — claim, evidence, counterclaim, formal style | Yes — full process | Fri Mar 12 |
Spring Break Mar 15–26 follows immediately. If MLK Day or Presidents' Day become school make-up days, they're catch-up days here, not new-lesson days.
The point of this quarter: a sustained project of her choosing that uses the whole year's toolkit and ends in real publication. Lessons in Q4 mostly serve the project — mini-lessons on whatever the work needs that week — plus portfolio and reflection at the end.
This quarter's strategy work: no new strategy — independence. The year's hand-over completes: she chooses which planner the capstone needs and runs it herself; mini-lessons revisit a strategy only when the work shows it's needed.
| Deliverable | Due |
|---|---|
| Capstone chosen + one-page proposal (what, for whom, what finished looks like) | Fri Apr 2 |
| Project plan: outline / chapter list / scene list | Fri Apr 9 |
| Midpoint check-in: half the project drafted; scope adjusted honestly if needed | Fri Apr 30 |
| Full draft complete | Fri May 7 |
| Revision + production (illustrations, formatting, printing) | Fri May 14 |
| Capstone published — printed, bound, performed, or premiered for the family | Fri May 21 |
| Final week: portfolio assembly, side-by-side August-vs-May comparison, her own written reflection on the year, celebration | May 24–28 |
The tracker is the course's steering signal: a short list of current teaching points, drawn from her actual work, that daily drills and lesson choices aim at. It lives here and gets updated by the evaluation protocol (§7). Keep it to 3–5 active items — more than that and nothing gets focused attention. When an item stops appearing in her drafts for three consecutive pieces, retire it (move it to "Secured") and promote something new.
| Teaching point | Evidence from her work | How we're fixing it | Retire when… |
|---|---|---|---|
| Comma splices & run-ons | "She really wanted to go forward but she couldn't, she was frozen with fear." | Daily sentence-combining drills using her own sentences; never worksheets | Absent from three consecutive final drafts |
| Telling instead of showing | "with fear in his voice," "Clara was shocked," "he said emotionally" | Lesson 3 + ongoing; drill: rewrite one "told" emotion per day as action/dialogue | Named emotions rare in drafts, not just revisions |
| Repetitive sentence openers | Runs of "The dragon… / Clara… / She…" | Subordinate-clause opener drills; "no more than two sentences in a row start the same way" as a product goal | Varied openers appear in first drafts unprompted |
| Dialogue conventions | "can I try to help?", "The dragon said" | One dialogue-mechanics lesson + a pocket reference card; checked in edit passes | Clean dialogue in two consecutive pieces |
| Paragraphing | Draft was mostly one-sentence paragraphs; she began merging in revision — she's ready | Explicit paragraph lesson; "group these sentences" drill | Deliberate multi-sentence paragraphs in first drafts |
Lessons are generated the morning of (or the night before), one or two at a time, by you + the AI, using this recipe. This is the section to reference when you sit down and say "make today's handout."
Craft techniques change lesson to lesson; strategies — the named, reusable procedures for planning and revising — run on a quarterly cycle instead. Each §4 card names the quarter's one strategy. The teaching arc, per SRSD: talk it through → model it aloud → she memorizes it → supported use → independent use. Two rules make it stick: advance by criterion, not calendar — a strategy is learned when she reaches for it unprompted on a new piece — and pair it with self-regulation: she sets the piece's goal from the strategy, checks her own steps off before handing work in, and says afterward what worked. Handouts reference the current strategy by name whenever the assignment involves planning or revising.
The mini-lesson is a demonstration, not a reading. Before she uses the technique, try it yourself in front of her on a sentence or two of your own — thinking aloud, false starts and crossed-out verbs included. The messy middle is the lesson: a classroom teacher can rarely afford it; you can. (Model → practice → reflect is the strongest-evidence teaching cycle in the secondary-writing practice guide.)
/lessons in a project session. It reads this plan (current quarter card in §4,
this template, the steering rules in §8), STATUS.md, and the log tail, picks the technique the
tracker most needs, and writes the handout as a self-contained printable HTML
file in writing/lessons/ — HTML only, no PDFs are created or kept; print from the
browser (Cmd-P) when needed. Variants: /lessons 3 for a coherent mini-sequence ·
/lessons 2 she's obsessed with Wings of Fire, lean into it for count + steering ·
/lessons redo N <reason> to regenerate an existing handout in place.
Customization is expected at this step, every day — swap the mentor text, change the topic to this week's obsession, halve the assignment on a low-energy day, or abandon the plan entirely because she asked a great question yesterday. The technique-menu items are the checklist; the order and flavor are yours.
Completed assignments land in writing/completed/ (established format: planning
answers + rough draft + completed version in one file; she works in Google Docs and sends the
doc when finished — it's printed for her and archived here). Then, together with the AI:
What we deliberately don't do: mark every error (teaches that writing is error-avoidance), grade individual pieces (feedback beats grades in the research), or fix her sentences for her (the comma splices fall to focused drills, not red ink). Freewrites and journals are never evaluated at all.
In the last week of each quarter: re-read the quarter's completed folder together, pick her best piece and her favorite piece (they may differ — good conversation), write a short growth memo (what improved, with before/after quotes; what's next), and update the tracker and next quarter's plan. If a grade is ever needed for records, it's assigned holistically from the quarter's body of work at this review — mastery of the quarter's techniques, completion of milestones — not averaged from pieces.
This plan is a starting map, and the territory will disagree with it. Rules for changing it:
| Date | Version | Change |
|---|---|---|
| Aug 5, 2026 | 1.0 | Initial course plan, built from the August research notes, the 2026–27 school calendar, and the baseline assessment of Lessons 1–2. |
| Aug 6, 2026 | 1.1 | Brought up to the print standard (dev/how-to-print.html): standard print block added, tables given real header rows. §6 daily prompt replaced with the /lessons skill invocation — handouts are HTML-only, printed on demand, no stored PDFs. Day-to-day operation now runs via the /lessons and /evaluate skills with STATUS.md + LOG.md state (spec: dev/skills-build-plan-for-writing.html). |
| Aug 6, 2026 | 1.2 | Freewrite policy corrected (§3 table, §6 template): still never graded and rule-free — stream-of-consciousness, any topic — but turned in with the day's work, not kept private. Skeleton comment updated to match. §7 unchanged: freewrites are still never evaluated. |
| Aug 7, 2026 | 1.3 | Aligned with the evidence review (teaching-writing-research-2.html), which post-dates this plan's sources. Four additions: (1) one named strategy per quarter, taught SRSD-style to independence — strategy lines on each §4 card, through-line + checklist hook in §6, goal #2 updated; (2) live modeling — mini-lessons demonstrated with a think-aloud, and the parent writes alongside her some days (§3, §6); (3) weekly conference, writer talks first — new §3 row, §7 reframed so the feedback note records the conversation; (4) write-together as a standing weekly move (§3). Documented the existing drafting workflow: Google Docs → send → printed copy + chat copy (§3, §7). Small fixes: §2 drill time matched to §3 (ten minutes); Q2 summarization ranking corrected (tied for strongest, not #2); stale "next is Lesson 4" pointers now defer to STATUS.md; companion line names both research documents. |