Use Claude Opus 5.5 to draft and revise a music video plan, then check that plan against your actual recording before generating visuals. The useful output is a clear set of creative decisions: what happens, where each scene belongs, and which details must remain consistent.
Anthropic announced Opus 5.5 on September 22, 2026 and describes improvements in professional work and agent tasks. That makes it relevant to explore as a planning assistant, but the announcement is not evidence of music-video quality or a built-in connection to your song library. Anthropic's Opus information.
The prompts and scene examples below are original planning exercises. They are not outputs from a paid Opus test or a claim that Claude rendered a finished video.
Give the planner a brief it can actually use
Start with information you have verified yourself. If you supply only a song title, the planner has to guess the structure, lyrics, mood, and production constraints.
Prepare a small brief containing:
- The selected song version and its duration.
- Accurate lyrics, or a section summary when you do not want to provide the full text.
- Section boundaries you marked while listening.
- The intended video format and the viewer's main focus.
- Available visual assets and practical limits.
Use content you can share with the service. Do not assume that pasting a private Suno link gives Claude access to the recording or proves it listened to it. State which information comes from your own notes, and ask the planner to flag missing inputs instead of inventing them.
A fictional brief could be:
Project: a lyric-led music video for an original song about returning home.
Recording: selected final mix, 2 minutes 40 seconds.
Section timings: I will provide the actual boundaries below.
Visual direction: a quiet coastal town after rain, restrained blue and amber colors.
Recurring subject: one adult cyclist wearing a tan coat and carrying a green bag.
Production limits: one recurring character, three locations, no crowds,
no readable signs, and no close-up singing performance.
Viewer priority: read the lyrics comfortably.
Available assets: no approved reference images yet.
Those limits are creative choices for this example, not model restrictions. They make the first plan easier to evaluate and less likely to demand a different cast or environment for every line.
Ask for a treatment before a long shot list
A treatment is a short account of what the viewer will see across the song. It lets you reject the wrong story before it grows into dozens of detailed prompts.
Try this request:
Using only the supplied brief and section notes, propose two distinct visual
approaches. For each, describe the opening image, the recurring visual idea,
and the ending in one short paragraph. Explain how the approach leaves room
for readable lyrics. Identify any missing information. Do not invent song
lyrics, timestamps, existing assets, or claims that you listened to the audio.
Choose the approach that fits the recording. For the coastal-town brief, one approach might follow the cyclist toward a lit window; another might use recurring views of the empty bicycle as the surroundings change. They imply different production tasks even if both express returning home.
Avoid selecting a plan solely because its description sounds impressive. A sudden underwater city, a large parade, or several costume transformations may introduce work that does not help this particular song.
Convert the chosen treatment into a reviewable storyboard
Now ask for a compact table. Each row should explain a scene's role, not just list visual adjectives.
Expand the chosen treatment into a storyboard using the section boundaries
I supplied. Include: section, visual purpose, observable action, camera view,
continuity requirements, and space reserved for lyrics.
Use a small number of scenes. Keep the same subject and established locations.
Label assumptions. If a proposed action cannot fit the supplied section,
suggest simplifying it rather than silently changing the timing.
An illustrative row might be:
| Field | Planning example |
|---|---|
| Section | First verse, using the supplied timing |
| Visual purpose | Establish the cyclist's hesitation |
| Action | The cyclist stops at a corner and looks toward a lit window |
| Camera view | A stable medium-wide view from across the street |
| Continuity | Tan coat, green bag, same bicycle |
| Lyric space | A quiet wall area away from the subject and bright window |
The row gives you several things to inspect. Can the action be understood without dialogue? Is the lyric area actually quiet? Does the next scene begin from a plausible position? If the row cannot answer those questions, refine it before requesting detailed generation prompts.
Audit the plan for invented facts and hidden work
Read the storyboard once as an editor and once as the person who must produce it.
| Problem in the draft | Revision to request |
|---|---|
| Timings were invented despite missing section notes | Remove them and list the timing information still needed |
| A new outfit appears halfway through | Restore the approved appearance or explain an intentional change |
| Every line introduces a new place | Consolidate locations around the song's larger sections |
| A scene depends on exact readable text inside generated imagery | Move the text into the editing plan |
| The plan describes a singing close-up you did not request | Replace it with a non-singing action or identify the extra synchronization task |
| A transition assumes an unavailable reference image | Mark that image as an asset to prepare, not an existing input |
For the cyclist example, the bag should not become a suitcase merely because the second verse uses a travel metaphor. A literal illustration of every lyric can also make the visual story harder to follow. Ask for a consistent interpretation rather than treating every line as a separate assignment.
Request scene prompts only after the storyboard works
Use the approved row as the source for one scene prompt at a time. Keep the model-specific controls outside the general creative brief until you know which video tool will receive it.
Turn this approved storyboard row into a plain-language scene prompt.
Describe the subject, setting, one principal action, framing, and lighting.
Keep all approved continuity details. Do not invent parameter names, reference
tags, duration limits, or features of the video model. List any settings that
must be chosen separately in the actual generation interface.
This avoids a common handoff problem: a useful story wrapped in technical syntax that belongs to another tool. Our Seedance timestamp guide explains one specific timing workflow; our reference-image guide distinguishes appearance guidance from fixed frames. Use the documentation for your selected model when translating the brief into controls.
Generate or prepare a representative scene before committing to the whole plan. Choose one with a recurring subject and a substantial lyric line so the review tests both continuity and readability.
Revise from concrete output, not vague disappointment
When a candidate fails, describe the visible problem and ask for a bounded change. For example:
The cyclist is readable, but the bright window sits behind the lyric area.
Keep the character, action, and location. Propose two framing changes that
move the window away from the text. Do not add a new scene or change the song.
If you have not provided the actual image or clip in a supported form, say that this is your observation. Do not invite the planner to pretend it saw an unavailable file.
Keep the accepted storyboard separate from exploratory revisions. A small note such as “Scene 2 framing approved; window moved to the right” makes it easier to resume later without treating every new suggestion as the current plan.
Hand off the plan to the video workflow
A storyboard does not establish lyric synchronization, final audio balance, or a successful export. Keep the selected recording as the timing reference and review the finished file outside the editor.
LyricVideoMaker provides an audio-upload and editable lyric-video workflow. You can use an externally prepared creative brief to guide your choices; this article does not claim that Claude or Opus 5.5 is integrated into the product. For the full sequence from source audio to reviewed export, see turning a song into a music video.
Does a stronger language model remove the need to review the plan?
No. Check the lyrics, section timings, available assets, and visual continuity yourself. A polished description can still contain an impossible transition or an invented assumption.
Should I ask for the entire video in one prompt?
Start with a treatment, approve the storyboard, then develop individual scenes. That gives you useful points at which to correct the direction before producing assets.
What is a good stopping point for the planning session?
Stop when each scene has a clear purpose, an action you can describe, a plausible place in the song, and a known next production step. More prose is not necessarily a more usable storyboard.