Start with a three-scene Scratch comic — English carousel cover for this classroom case

Parents ask it often: how do kids finish what they start? In our Markham classroom the honest answer is simple — write the finish line before you open the editor. Do not keep adding scenes until the first three play clean. Four questions on paper beat one more backdrop.

A real classroom case: Scratch three-scene comic stuck after scene 1

Last month at afterschool in Markham we had a Scratch three-scene comic. Scene 1 looked great. Scenes 2 and 3 never landed. One classmate kept opening new backdrops instead of finishing. We paused and wrote four questions on paper before opening Scratch again.

Once those four answers are clear, the finish line stays clearer than “one more scene.” The typing (or the clicking) is the fast part. Our 2026-09-23 Xiaohongshu note used this exact classroom beat: write the finish line first, then build — do not keep adding scenes until the first three play clean.

Why this still matters when AI can write code

Claims below are grounded in that teaching note — not an external product case with published accuracy metrics.

1. AI does not remove the need to name the finish line. “Tell a 3-scene story a classmate can follow” is a different job from “make any comic look cool.” If a kid (or an AI prompt) muddles those, the next scene that comes back solves the wrong problem.
2. The useful state is tiny on purpose. You only hold three titles → scene 1 → scene 2 → scene 3 → play once. That is abstraction: keep what the next build needs, drop the rest.
3. The done rule and edge cases are the algorithm. The same four questions transfer to science fair poster sections, a birthday party timeline, or a team practice drills list. Contest-style questions inspired by CCC Junior, CCC, BCC, and school contests reuse those moves — kids who want to sit those register on their own; CodeSky is not an official contest program and is not affiliated with Waterloo or CEMC.
4. Languages are tools on a path, not the answer. Early work often uses Python so the steps stay readable; JavaScript when the same idea becomes something clickable on a screen; C++ later when speed and structure matter. Tools change; the finish line does not.

So AI’s ability to type code does not cancel a thinking-first start. It raises the value of kids who can write the finish line, hold the right state, and check the edge cases before they ask a model to type — and before they add scene 4.

Three steps kids can name

We practice the same shape on the bench:

1 · Write — the finish line and four questions before Scratch

2 · Transfer — same finish line to science board, party, practice

3 · Finish — three scenes before adding more

• Decomposition — goal → state → done rule → special cases
• Abstraction — keep only three titles → scene 1 → 2 → 3 → play once
• Algorithms — titles → build → play → handle missing backdrop / friend wants scene 4 / sound gone / save failed
• Pattern recognition — same four questions in science board sections, birthday party timelines, team practice checklists, contest-style I/O

Follow CodeSky

Instagram @codeskyca  ·  小红书 / RedNote  ·  WeChat 公众号: search codeskyca

Sources: CodeSky Xiaohongshu note pack 2026-09-23-孩子做项目总是半途而废怎么办 (Scratch three-scene comic case; Python → JavaScript → C++ pathway; contest-style disclaimer).