Repository navigation
docs(rich): have the critic read a light storyboard before the film is written - #89
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
/motion-render:richnow has a critic read a light storyboard before the film is written.The final critic pass on the contact sheet stays. Its job is now drawing and motion. What a scene shows is already settled before the film is written.
Part of #87.
Why
In the benchmark run in #87, 7:13 of the 48 minutes went to applying the critic's top 3 and verifying again. All three findings were about what the scenes show, and they could have been caught before the film existed. The guide asked for a
plan.md, but nothing reviewed it, and that run skipped it.Experiments in #87
Changes
skills/rich/SKILL.mdplan.md(the intent, a few lines, never shown to the critic) andstoryboard.md(only the five per-scene fields). Step 4 starts the storyboard critic in the background withbgm. Step 5 reads the kit and arranges the score while the critic reads, fixes the storyboard's worst 3, then writes the film. Step 7's critic now looks at drawing and motion.references/html-film.mdstoryboard.md, the narration and the scene times, notplan.md. (2) The final review onsheet.png, unchanged, plus a note to check that a finding is not only an artifact of the sampled frame times. "絵コンテと秒の計画" and "場面を分けて書く" now point atstoryboard.md.references/pipeline.mdMeasured
One trial run (2026-11-18) followed this procedure. It made a 66.9 s film at 124 BPM, with one stop, two drops, 5 sound effects and a 42.0 KB film page. Last time the page was 42.7 KB.
motion-render timesfor the trial: total 28 min 55 s from the first command, Claude 25 min 20 s, waiting on commands 3 min 34 s. The details are in the trial comment on #87.The comparison has two caveats:
Test plan
make checklayout: ok,sync: ok