← PicsartCONTENT HISTORY

Update to Picsart

Snapshot Nov 11, 2026 · 00:08 UTC · version 2.5.0

Collection source: downloaded plugin package.

WHAT CHANGED

Instructions updated for movie-producer

Full description — Now says: story, with recurring characters, one look and approved cast/location references, then draft video and a reviewed cut. Storyboard or animatic only on...

Observed in instructions or declared skills. Runtime behavior has not been tested.

Save Picsart and check future changes in Following.

Up to 3 plugins free · no card required.

All fields and original values.

Full description

Before

Nov 7, 2026 · 00:09 UTC

story - several scenes, recurring characters, one locked look - staged and approved step by step, drafted as an animatic before video. Use when the user wants a short film, a movie or a multi-scene story ("I have a script"), or carries o...

After

Nov 11, 2026 · 00:08 UTC

story, with recurring characters, one look and approved cast/location references, then draft video and a reviewed cut. Storyboard or animatic only on explicit request. Use for short films, movies, multi-scene scripts, or continuing an ex...

Skill instructions

Before

Nov 7, 2026 · 00:09 UTC

story - several scenes, recurring characters, one locked look - staged and approved step by step, drafted as an animatic before video. Use when the user wants a short film, a movie or a multi-scene story ("I have a script"), or carries o...

After

Nov 11, 2026 · 00:08 UTC

story, with recurring characters, one look and approved cast/location references, then draft video and a reviewed cut. Storyboard or animatic only on explicit request. Use for short films, movies, multi-scene scripts, or continuing an ex...

Supporting files

Before

Nov 7, 2026 · 00:09 UTC

[{"relative_path":"agents/openai.yaml","size_in_bytes":176},{"relative_path":"references/board-replies.md","size_in_bytes":5697},{"relative_path":"references/project-record.md","size_in_bytes":6163},{"relative_path":"references/stages.md...

After

Nov 11, 2026 · 00:08 UTC

[{"relative_path":"agents/openai.yaml","size_in_bytes":176},{"relative_path":"references/board-replies.md","size_in_bytes":6328},{"relative_path":"references/project-record.md","size_in_bytes":9147},{"relative_path":"references/stages.md...

Compare saved observations

Download comparison JSON

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -1,9 +1,9 @@
 ---
 name: movie-producer
-description: Make a short narrative film from a story - several scenes, recurring characters, one locked look - staged and approved step by step, drafted as an animatic before video. Use when the user wants a short film, a movie or a multi-scene story ("I have a script"), or carries on a film already under way here (its shot list, a change to one shot, or the next step). Load it first for any work on such a film; it brings in the film skills each step needs. Not for a drama series or its episodes (make-short-drama), a single clip, or footage the user already has.
+description: Make a short narrative film from a story, with recurring characters, one look and approved cast/location references, then draft video and a reviewed cut. Storyboard or animatic only on explicit request. Use for short films, movies, multi-scene scripts, or continuing an existing film (shot list, shot changes or next step). Load first; it brings in the film skills for each stage. Not for a drama series or its episodes (make-short-drama), a single clip, or footage the user already has.
 metadata:
-  uses: film-story-writing, film-cast-design, film-shot-generation, film-animatic, voice-over-generation, film-cutting, film-finishing, footage-reframing, background-music, scene-building-basics, quality-review, realistic-color-grade, sd25-pe, sd2-pe
-  optional: realistic-color-grade
+  uses: film-story-writing, film-cast-design, film-shot-generation, film-cutting, film-finishing, footage-reframing, background-music, scene-building-basics, quality-review, realistic-color-grade, sd25-pe, sd2-pe, film-animatic, voice-over-generation
+  optional: realistic-color-grade, film-animatic, voice-over-generation
   title: Produce a short film
   short-description: Make a short film from your story, scene by scene
   argument-hint: '[story idea or script]'
@@ -14,14 +14,18 @@
 
 A film is not a long video. The model has no memory between generations: describe a character
 loosely and he arrives in every shot with a different face, jacket and age. Everything here exists
-to beat that one problem, consistency, and it runs on one economic law: **stills are cheap, video
-is expensive.** Every decision that can be made on text, pictures and sound is made there: the
-user watches the film as a voiced animatic, and says yes to it, before the first video is bought.
+to keep those people and places consistent. Lock the story, shot list, cast and location references,
+then shoot draft video directly. The first moving draft the user reviews is the assembled cut.
+Storyboard panels and an animatic are made only when the user explicitly requests them. They are
+not part of the default flow, and are never offered as another decision before shooting.
 
 Read picsart-video-rules first. One job: a story in, a short film out, with recurring people and places
 and one look.
 
 Before acting on a stage, load the skills in its row that apply to this job, also when the work resumes there.
+`(preview-requested)` applies only to an explicit request for a storyboard or animatic;
+`(animatic-requested)` only to an explicit animatic request. These skills and the preview REVIEW
+are otherwise skipped; the location references are still prepared.
 
 | Stage | Gate | Skills |
 |---|---|---|
@@ -29,12 +33,11 @@
 | 2. The look | ASK | film-story-writing |
 | 3. The story and the model | ASK | film-story-writing, film-shot-generation, sd2-pe, sd25-pe |
 | 4. The shot list | ASK | film-story-writing, film-shot-generation |
-| 5. Cast, places and props | SPEND, ASK | film-cast-design |
-| 6. Storyboard and animatic | SPEND, ASK, REVIEW | film-animatic, film-shot-generation, film-cast-design, voice-over-generation, scene-building-basics, quality-review |
-| 7. Shooting | SPEND, ASK | film-shot-generation |
-| 8. The cut | SPEND, ASK, REVIEW | film-cutting, scene-building-basics, quality-review |
-| 9. Finishing | SPEND, ASK, REVIEW | film-finishing, background-music, realistic-color-grade |
-| 10. Deliver | ASK, DELIVER | film-finishing, footage-reframing |
+| 5. Cast, places and props | SPEND, ASK, REVIEW (preview-requested) | film-cast-design, film-shot-generation, scene-building-basics, film-animatic (preview-requested), voice-over-generation (animatic-requested), quality-review (preview-requested) |
+| 6. Shooting | SPEND, ASK | film-shot-generation |
+| 7. The cut | SPEND, ASK, REVIEW | film-cutting, scene-building-basics, quality-review |
+| 8. Finishing | SPEND, ASK, REVIEW | film-finishing, background-music, realistic-color-grade |
+| 9. Deliver | ASK, DELIVER | film-finishing, footage-reframing |
 
 Read these before you need them:
 
@@ -56,7 +59,7 @@
 | A film already under way (a project record) | Resume: read the record, say where the film stands, continue at its stage |
 
 **Pace: director by default**, as picsart-video-rules says. In express pace the user comes in only for the
-boards, the three locks (the look, the story with its model, the assets), the animatic's review, every charged call no stated spend limit covers and
+boards, the three locks (the look, the story with its model, the assets), the cut's review, every charged call no stated spend limit covers and
 anything beyond a quote.
 
 ## How you talk to the user
@@ -65,7 +68,7 @@
 
 - one board per decision; everything else waits in the record's `openDecisions`;
 - what each board's reply holds is in `references/board-replies.md`;
-- where things stand reads like "Stage 5 of 10 · cast, places and props — locking Cal (2 of 5
+- where things stand reads like "Stage 5 of 9 · cast, places and props — locking Cal (2 of 5
   done)", and the gate view shows which scenes have everything they need ("not ready yet", never
   "a hole");
 - an alarm word is for a real gate violation, such as a video about to be bought for a scene
@@ -77,7 +80,7 @@
 files, keep it as `film.json` in the working folder; otherwise keep it in the conversation and
 give it to the user once, at the end of a working session, to paste back next time. Never print it
 mid-flow. Update it whole at every milestone: a gate passed, an asset locked, a batch dispatched or
-landed, a review round, picture lock, the export. Its shape is `references/project-record.md`.
+landed, a review round, picture lock, the export. Its shape and the migration of older ten-stage records are in `references/project-record.md`.
 
 Beside the facts it keeps the **brief**: the logline, the world in three sentences, the people as
 people, and the standing decisions with their reasons ("hard cuts only: the film is about
@@ -100,8 +103,8 @@
 
 **The challenger at each decision.** Before you go on from a decision, quality-review's challenger (the
 `challenger` agent where the host has it) asks "why this?" of it: the idea (stage 1), the look and
-the story (2, 3), the shot list (4), each sheet, plate, scene picture and panel picked and why (5, 6), and
-every quote before its SPEND (5, 6, 7, 9, and a repair in 8 that needs a generation). Act on its
+the story (2, 3), the shot list (4), each sheet, plate, scene picture and location map picked and why (5), and
+every quote before its SPEND (5, 6, 8, and a repair in 7 that needs a generation). Act on its
 verdict as quality-review says. A `stop`, or a `rethink` of the user's own choice, goes to the user in the
 next ASK, the cheaper alternative first, before anything is spent.
 
@@ -174,6 +177,26 @@
 sentence on the shot that opens each run. Pass `film`, the model, and the setup's defaults, so the
 user never picks from a vocabulary the film has not adopted.
 
+**Use the model's capacity before opening the board.** Load film-shot-generation's Runs method
+and its seams reference. Read the selected model's accepted durations and reference limits from
+`picsart_model_params`, then pack the ordered shot cards into the fewest runs that fit, across
+scene boundaries. Assign run ids only after packing: the board preserves those boundaries, so
+one id per beat would lock in needless generations. Several cuts belong inside one generation;
+a climax, a close-up, a new scene or "easier to generate" is no reason to split it.
+
+Check each boundary: can the next shot fit in the preceding run within the model's duration and
+reference limits? If yes, keep packing; if no, record the limiting constraint. Preserve shot order,
+shot lengths and dialogue; do not stretch shots or add filler to reach the ceiling. The final
+remainder can be short. A shorter run otherwise needs a specific model limit or the user's explicit
+split. For example, six proposed runs of 7, 7, 4, 3, 6 and 3 seconds become one 30-second generation
+when the selected model accepts 30 seconds and their combined references fit. The nine shot
+cards and their internal cuts stay separate inside that generation.
+
+Write the internal cut pairs and each necessary run edge using film-shot-generation's seams
+reference: match action, eyelines and screen direction, keep geography, and carry frames only
+for its named exceptions. Fewer generations must preserve this method, not replace the cuts
+with one long shot or buy a bridge for every boundary.
+
 - The board approves camera and seconds. It is not a place to rewrite the story: an edit that
   changes what happens is a story note, so rewrite the paragraph first, then open the board again.
 - On `shotlist_board_feedback`, **replace** your list with it, runs included. Fields the board does
@@ -212,51 +235,93 @@
 4. Look at each picture (picsart-video-rules, Asset URLs) before anything uses it, then put them all on
    `picsart_film_review_assets` in one call (at most 12 tiles; more go on a second board), with the one thing to judge them by as the board's `judge`, and one line per tile as its `assets[].why`.
 5. Act on the reply as `references/board-replies.md` says. Each approved asset is cut into views and
-   locked with `picsart_film_save_asset`, as film-cast-design says. A change is regenerated under its own SPEND and put on a fresh board with `assets[].version` and
-   `assets[].previousUrl`. A discarded tile is never used.
+   locked with `picsart_film_save_asset`, as film-cast-design says. Before regenerating a rejected
+   picture, save that version as `rejected` and record it as below. The replacement is regenerated
+   under its own SPEND and shown alone on a fresh board, with `assets[].version`; omit `assets[].previousUrl` when the previous picture
+   was rejected. A discarded tile is recorded as rejected and never used.
 
 A person the user photographed is saved as it came and is not put up for approval: it is theirs.
 film-cast-design flags what it cannot settle on its own, about a photo the user brought or about the
 film's era. Raise each flag once, as one short ASK (with the host's own choice tool where it offers one, such as request_user_input in Codex's Plan mode, so the user taps an option; a Picsart board the step names asks there instead; only where neither works, the options numbered in one message, the recommended one first; in unattended pace, never ask: write it to the project record's openDecisions with the answer you assumed, as picsart-video-rules says) with the options film-cast-design names. Anything
 generated is its own SPEND.
 
-## 6. Storyboard and animatic
+### A rejected cast picture
 
-The film is drafted on stills and sound, and the user watches it before any video is bought. Load
-film-animatic before you say what this stage needs or ask anything in it. Its yes is the gate into
-shooting.
-
-1. **Scene pictures.** Every scene gets its pictures: the wide, the scene picture cut from it,
-   and a room map where the scene cuts between walls, as film-shot-generation says. The scene
-   picture is the scene's opening panel and the opening frame of its first run.
-2. **One panel per shot**, compiled from its card and checked against its scene picture, as
-   film-animatic says. A real app's screen in a shot is built as a scene layer from the user's
-   own screenshots or recording, never generated. **One SPEND (quote it in one line, then get the yes as an ASK with "Yes, go ahead" / "Yes, up to N credits for this task" / "No": the host's own choice tool where it offers one, otherwise those options numbered in one message; the host's own confirmation before a tool runs is not this yes; unless a spend limit the user stated covers it: N credits or an explicit no-limit ("as much as needed"), never inferred from words like "go ahead". Within it, ask nothing: quote it in one line ("About 8 credits; 12 of 20 left after this"), call it, then say what it spent and what remains, keeping a running total that includes failed calls, and stop to ask before the first call that would cross it. A money amount is asked once to restate it in credits; in unattended pace, never ask: call only with a consent or a stated spend limit already recorded, otherwise write the quote to pendingSpends and stop, as picsart-video-rules says) for every scene picture and
-   panel**, batched as picsart-video-rules says (at most 10 a call), and
-   `picsart_film_review_assets` for all of them, 12 tiles a board.
-3. **The sound**: every line in its person's voice, a bed per scene and the card's effects, as
-   film-animatic says, on one SPEND (quote it in one line, then get the yes as an ASK with "Yes, go ahead" / "Yes, up to N credits for this task" / "No": the host's own choice tool where it offers one, otherwise those options numbered in one message; the host's own confirmation before a tool runs is not this yes; unless a spend limit the user stated covers it: N credits or an explicit no-limit ("as much as needed"), never inferred from words like "go ahead". Within it, ask nothing: quote it in one line ("About 8 credits; 12 of 20 left after this"), call it, then say what it spent and what remains, keeping a running total that includes failed calls, and stop to ask before the first call that would cross it. A money amount is asked once to restate it in credits; in unattended pace, never ask: call only with a consent or a stated spend limit already recorded, otherwise write the quote to pendingSpends and stop, as picsart-video-rules says), each voice line's real length probed before anything is
-   timed to it.
-4. **The animatic**: built, validated, cut-checked, looked at and watched cold as film-animatic says
-   (quality-review's cold watch, quoted first with its own SPEND (quote it in one line, then get the yes as an ASK with "Yes, go ahead" / "Yes, up to N credits for this task" / "No": the host's own choice tool where it offers one, otherwise those options numbered in one message; the host's own confirmation before a tool runs is not this yes; unless a spend limit the user stated covers it: N credits or an explicit no-limit ("as much as needed"), never inferred from words like "go ahead". Within it, ask nothing: quote it in one line ("About 8 credits; 12 of 20 left after this"), call it, then say what it spent and what remains, keeping a running total that includes failed calls, and stop to ask before the first call that would cross it. A money amount is asked once to restate it in credits; in unattended pace, never ask: call only with a consent or a stated spend limit already recorded, otherwise write the quote to pendingSpends and stop, as picsart-video-rules says) unless every call is quoted at
-   0 credits), then REVIEWed in the scene editor,
-   with its sound, opened cold. Notes route as film-animatic says: a story note
-   goes back to stage 3's paragraph, a shot note to that panel or line alone, each change made
-   again under its own SPEND. Loop until the user says yes.
-
-**No still test.** The scene pictures are where the cast is checked, as film-cast-design says, and
-so are the panels: say in their review what you saw in each face. A change to a person or a prop goes back
-through stage 5's conveyor alone, under its own SPEND, on a fresh board.
-
-**The gate into shooting:** the animatic approved, film-cast-design's gate into a run held for every
-run, and every scene it spans with approved pictures. A user who wants to shoot without the
-animatic may, as a recorded override; never skip it yourself.
-
-## 7. Shooting
-
-**Which shots go to video is the user's.** ASK (with the host's own choice tool where it offers one, such as request_user_input in Codex's Plan mode, so the user taps an option; a Picsart board the step names asks there instead; only where neither works, the options numbered in one message, the recommended one first; in unattended pace, never ask: write it to the project record's openDecisions with the answer you assumed, as picsart-video-rules says) once, all shots recommended unless the
-animatic showed a held panel works as it is; a shot kept as a panel stays in the cut as approved.
-Quote only the picked shots, each opening on its approved panel, as film-animatic says.
+Treat "Change one", "not her", "profile is not ok", "it's not her", or any no to a cast picture
+as a rejection. If several pictures were shown and the target is unclear, ASK (with the host's own choice tool where it offers one, such as request_user_input in Codex's Plan mode, so the user taps an option; a Picsart board the step names asks there instead; only where neither works, the options numbered in one message, the recommended one first; in unattended pace, never ask: write it to the project record's openDecisions with the answer you assumed, as picsart-video-rules says) which one
+without showing them again; do not regenerate until it is identified.
+
+Before regenerating, call `picsart_film_save_asset` for the rejected version with `status: "rejected"`,
+its original `tag`, `sheetVersion`, `portraitUrl`, `projectFolderUid` and saved asset metadata.
+Pass the saved `identityReferences` too. Every new save supplies the user's original photo URLs
+there, or `identityReferences: []` when all views are generated. Do not infer provenance from a
+view's position; preserve unknown provenance on older records.
+Record its tag, version, file uid, URL and all extracted view/panel URLs in the project's
+`rejectedAssets[]`, and mark that version's asset row `rejected`. Confirm the save succeeded before
+a replacement is generated; on failure keep the local rejected entry and retry the save, never reuse it.
+A replacement gets a new version and stays in review until the user approves it.
+
+Never show a rejected picture again, including in a comparison, `previousUrl`, an old plan card or
+an asset recap. Never pass any part of it as a reference: no full-body front, profile, crop, view
+or panel. Rejecting one view rejects the whole sheet unless the user explicitly said otherwise;
+record any such exception and keep only the explicitly permitted view separate from the rejected sheet.
+Check `rejectedAssets[]` before every display, reference selection, plan and resumed film turn.
+Remove rejected references from pending opening frames and shot plans before continuing.
+
+For a person made from the user's own photos, keep those original photos in `identityReferences[]`
+and use them as the identity reference for every replacement. Rejecting a generated sheet never
+rejects the user's original photos; do not substitute a rejected generated face for them.
+
+### Location references before shooting
+
+Keep the location map. Follow film-shot-generation's scene-pictures reference: a wide for every
+scene, its opening scene picture cut from that wide, and a room map where the scene cuts between
+walls. Reuse one map per place and time of day; a single outdoor background uses its wide as its
+geography. Record the URLs in `scenes[].pictures` and the geography line in `scenes[].geography`.
+
+Compile and verify the required pictures, quote them together with SPEND (quote it in one line, then get the yes as an ASK with "Yes, go ahead" / "Yes, up to N credits for this task" / "No": the host's own choice tool where it offers one, otherwise those options numbered in one message; the host's own confirmation before a tool runs is not this yes; unless a spend limit the user stated covers it: N credits or an explicit no-limit ("as much as needed"), never inferred from words like "go ahead". Within it, ask nothing: quote it in one line ("About 8 credits; 12 of 20 left after this"), call it, then say what it spent and what remains, keeping a running total that includes failed calls, and stop to ask before the first call that would cross it. A money amount is asked once to restate it in credits; in unattended pace, never ask: call only with a consent or a stated spend limit already recorded, otherwise write the quote to pendingSpends and stop, as picsart-video-rules says), then generate the
+independent pictures in a batch. Check each before its board review, including the cast's faces,
+opening positions and room geometry. Use `picsart_film_review_assets` for the location references
+and apply `references/board-replies.md`. Reuse approved pictures already in the record. A real app's
+screen is built as a scene layer from the user's screenshots or recording, never generated.
+
+**No still test.** The scene pictures are where the cast is checked, as film-cast-design says.
+A cast or prop correction goes through that asset's conveyor only, under its own SPEND.
+
+**The gate into shooting:** the story and shot list approved, every scene in a run has approved
+location references, and film-cast-design's gate into a run holds for all its tags, read back from
+`picsart_film_list_assets`. The opening scene picture starts the scene's first run; later runs use
+film-shot-generation's continuity references. No storyboard panels, voiced slideshow or animatic
+approval is required in the default flow.
+
+### Only when the user requests a storyboard or animatic
+
+Record the explicit request in `requestedPreview` (`kind: "storyboard"` or `"animatic"`,
+`status: "requested"`) and load film-animatic for that work. A request for a **storyboard** uses
+its panel method only: quote and make the requested panels, check them, and review them on
+`picsart_film_review_assets`. It does not buy voices, music or a timed animatic. A request for an
+**animatic** uses its timed-preview method and voice-over-generation for its sound; quote the
+needed pictures and sound with SPEND (quote it in one line, then get the yes as an ASK with "Yes, go ahead" / "Yes, up to N credits for this task" / "No": the host's own choice tool where it offers one, otherwise those options numbered in one message; the host's own confirmation before a tool runs is not this yes; unless a spend limit the user stated covers it: N credits or an explicit no-limit ("as much as needed"), never inferred from words like "go ahead". Within it, ask nothing: quote it in one line ("About 8 credits; 12 of 20 left after this"), call it, then say what it spent and what remains, keeping a running total that includes failed calls, and stop to ask before the first call that would cross it. A money amount is asked once to restate it in credits; in unattended pace, never ask: call only with a consent or a stated spend limit already recorded, otherwise write the quote to pendingSpends and stop, as picsart-video-rules says), then validate, check and REVIEW the preview as that
+skill says. Reuse the approved cast and location references in either case.
+
+The request chooses the work, not permission for an unquoted spend. Apply SPEND (quote it in one line, then get the yes as an ASK with "Yes, go ahead" / "Yes, up to N credits for this task" / "No": the host's own choice tool where it offers one, otherwise those options numbered in one message; the host's own confirmation before a tool runs is not this yes; unless a spend limit the user stated covers it: N credits or an explicit no-limit ("as much as needed"), never inferred from words like "go ahead". Within it, ask nothing: quote it in one line ("About 8 credits; 12 of 20 left after this"), call it, then say what it spent and what remains, keeping a running total that includes failed calls, and stop to ask before the first call that would cross it. A money amount is asked once to restate it in credits; in unattended pace, never ask: call only with a consent or a stated spend limit already recorded, otherwise write the quote to pendingSpends and stop, as picsart-video-rules says) to every new
+charged operation. On approval, set `requestedPreview.status: "approved"` and continue to
+shooting; no second shot-selection question is added. Storyboards and animatics are never
+required, recommended as another gate, or created on a resume without that explicit request.
+
+## 6. Shooting
+
+Shoot the approved shot list directly, respecting any explicit exclusions the user already made.
+Do not ask them to choose the shots again. Use the approved scene-opening images and continuity
+references as film-shot-generation says; never require one generated panel per shot.
+
+**Recheck capacity before the forecast or quote**, including on resume. Reconcile the approved
+shot cards, current model limits and planned runs; show the generation count and each run's
+seconds against the ceiling. A batch with six items is still six generations. Do not quote
+mergeable short runs. If correcting them changes approved run boundaries, show that correction
+in the existing approval/quote step; keep the user's explicit splits, shot choices and seconds.
+Recompile the corrected runs and their joins, and replace the old quote. Never repack a submitted
+or completed job into another paid generation; keep its handle and existing footage.
 
 Before any run is quoted, a shot that film-shot-generation flags for a palette arguing with the film's
 scheme gets one short ASK (with the host's own choice tool where it offers one, such as request_user_input in Codex's Plan mode, so the user taps an option; a Picsart board the step names asks there instead; only where neither works, the options numbered in one message, the recommended one first; in unattended pace, never ask: write it to the project record's openDecisions with the answer you assumed, as picsart-video-rules says) with its options.
@@ -272,7 +337,7 @@
 3. **No film so far.** While takes run, never assemble, cut, open or show the film so far: a landed
    take waits for the others. As each take lands, find its actual cuts and judge it as
    film-shot-generation's takes reference says. That is your technical check, not acceptance:
-   every take stays a candidate until the user approves the cut (8). No question between the
+   every take stays a candidate until the user approves the cut (7). No question between the
    takes and the cut.
 4. Dialogue is judged in the cut's REVIEW, by ear. Say that the words were not checked against the
    script by a tool.
@@ -280,7 +345,7 @@
 Shooting is done when every take has landed and passed your check, with its actual cuts, prompt,
 quote and handle in the record. No take is accepted yet.
 
-## 8. The cut
+## 7. The cut
 
 When the last take lands, film-cutting assembles the film once: every candidate take in story order
 with hard cuts, every generation one clip exactly as generated: no split at a run's internal cuts,
@@ -297,7 +362,7 @@
 film-cutting's join repair says. Apply what the user points at, re-cut once and open it again, until
 they call it final. After that, change no picture unless they ask.
 
-## 9. Finishing
+## 8. Finishing
 
 In this order, as film-finishing says: the finish of the draft takes, then colour, then sound.
 
@@ -318,7 +383,7 @@
    track goes back through the background-music skill's brief, with a new SPEND. A film going to festivals
    or dubbing gets film-finishing's sound-team handoff offered once.
 
-## 10. Deliver
+## 9. Deliver
 
 DELIVER the final cut once, as picsart-video-rules says. Any further master from film-finishing's delivery
 list is confirmed with one ASK before the first is exported. A master in another shape is reframed as the
Full technical diff · 3 changed fields

changed /description

BEFORE
"Make a short narrative film from a story - several scenes, recurring characters, one locked look - staged and approved step by step, drafted as an animatic before video. Use when the user wants a short film, a movie or a multi-scene story (\"I have a script\"), or carries on a film already under way here (its shot list, a change to one shot, or the next step). Load it first for any work on such a film; it brings in the film skills each step needs. Not for a drama series or its episodes (make-short-drama), a single clip, or footage the user already has."
AFTER
"Make a short narrative film from a story, with recurring characters, one look and approved cast/location references, then draft video and a reviewed cut. Storyboard or animatic only on explicit request. Use for short films, movies, multi-scene scripts, or continuing an existing film (shot list, shot changes or next step). Load first; it brings in the film skills for each stage. Not for a drama series or its episodes (make-short-drama), a single clip, or footage the user already has."

changed /included_files

BEFORE
[
  {
    "relative_path": "agents/openai.yaml",
    "size_in_bytes": 176
  },
  {
    "relative_path": "references/board-replies.md",
    "size_in_bytes": 5697
  },
  {
    "relative_path": "references/project-record.md",
    "size_in_bytes": 6163
  },
  {
    "relative_path": "references/stages.md",
    "size_in_bytes": 8245
  }
]
AFTER
[
  {
    "relative_path": "agents/openai.yaml",
    "size_in_bytes": 176
  },
  {
    "relative_path": "references/board-replies.md",
    "size_in_bytes": 6328
  },
  {
    "relative_path": "references/project-record.md",
    "size_in_bytes": 9147
  },
  {
    "relative_path": "references/stages.md",
    "size_in_bytes": 8067
  }
]

changed /skill_md_contents

BEFORE
"---\nname: movie-producer\ndescription: Make a short narrative film from a story - several scenes, recurring characters, one locked look - staged and approved step by step, drafted as an animatic before video. Use when the user wants a short film, a movie or a multi-scene story (\"I have a script\"), or carries on a film already under way here (its shot list, a change to one shot, or the next step). Load it first for any work on such a film; it brings in the film skills each step needs. Not for a drama series or its episodes (make-short-drama), a single clip, or footage the user already has.\nmetadata:\n  uses: film-story-writing, film-cast-design, film-shot-generation, film-animatic, voice-over-generation, film-cutting, film-finishing, footage-reframing, background-music, scene-building-basics, quality-review, realistic-color-grade, sd25-pe, sd2-pe\n  optional: realistic-color-grade\n  title: Produce a short film\n  short-description: Make a short film from your story, scene by scene\n  argument-hint: '[story idea or script]'\n  starter-prompt: Make a short film from my story.\n---\n\n# Short film\n\nA film is not a long video. The model has no memory between generations: describe a character\nloosely and he arrives in every shot with a different face, jacket and age. Everything here exists\nto beat that one problem, consistency, and it runs on one economic law: **stills are cheap, video\nis expensive.** Every decision that can be made on text, pictures and sound is made there: the\nuser watches the film as a voiced animatic, and says yes to it, before the first video is bought.\n\nRead picsart-video-rules first. One job: a story in, a short film out, with recurring people and places\nand one look.\n\nBefore acting on a stage, load the skills in its row that apply to this job, also when the work resumes there.\n\n| Stage | Gate | Skills |\n|---|---|---|\n| 1. The idea | — | — |\n| 2. The look | ASK | film-story-writing |\n| 3. The story and the model | ASK | film-story-writing, film-shot-generation, sd2-pe, sd25-pe |\n| 4. The shot list | ASK | film-story-writing, film-shot-generation |\n| 5. Cast, places and props | SPEND, ASK | film-cast-design |\n| 6. Storyboard and animatic | SPEND, ASK, REVIEW | film-animatic, film-shot-generation, film-cast-design, voice-over-generation, scene-building-basics, quality-review |\n| 7. Shooting | SPEND, ASK | film-shot-generation |\n| 8. The cut | SPEND, ASK, REVIEW | film-cutting, scene-building-basics, quality-review |\n| 9. Finishing | SPEND, ASK, REVIEW | film-finishing, background-music, realistic-color-grade |\n| 10. Deliver | ASK, DELIVER | film-finishing, footage-reframing |\n\nRead these before you need them:\n\n| File | Read it before you… |\n|---|---|\n| `references/stages.md` | say a stage is done, or open the next one |\n| `references/board-replies.md` | act on a reply from any board |\n| `references/project-record.md` | write or resume the project record |\n\n## Before you start\n\n**Route first.** The dividing line is recurring identity across scenes.\n\n| The user brings | Route |\n|---|---|\n| One clip's worth of idea (\"a boot stepping onto scree\") | Not this use case. Say so, and offer one generation: `picsart_model_choose`, then SPEND (quote it in one line, then get the yes as an ASK with \"Yes, go ahead\" / \"Yes, up to N credits for this task\" / \"No\": the host's own choice tool where it offers one, otherwise those options numbered in one message; the host's own confirmation before a tool runs is not this yes; unless a spend limit the user stated covers it: N credits or an explicit no-limit (\"as much as needed\"), never inferred from words like \"go ahead\". Within it, ask nothing: quote it in one line (\"About 8 credits; 12 of 20 left after this\"), call it, then say what it spent and what remains, keeping a running total that includes failed calls, and stop to ask before the first call that would cross it. A money amount is asked once to restate it in credits; in unattended pace, never ask: call only with a consent or a stated spend limit already recorded, otherwise write the quote to pendingSpends and stop, as picsart-video-rules says) and `picsart_generate` |\n| Footage to cut together | Not this use case. Say it is not built yet here |\n| A story: scenes, people who recur, dialogue | This use case, from stage 1 |\n| A film already under way (a project record) | Resume: read the record, say where the film stands, continue at its stage |\n\n**Pace: director by default**, as picsart-video-rules says. In express pace the user comes in only for the\nboards, the three locks (the look, the story with its model, the assets), the animatic's review, every charged call no stated spend limit covers and\nanything beyond a quote.\n\n## How you talk to the user\n\nTalk and ask as picsart-video-rules says. Here that means:\n\n- one board per decision; everything else waits in the record's `openDecisions`;\n- what each board's reply holds is in `references/board-replies.md`;\n- where things stand reads like \"Stage 5 of 10 · cast, places and props — locking Cal (2 of 5\n  done)\", and the gate view shows which scenes have everything they need (\"not ready yet\", never\n  \"a hole\");\n- an alarm word is for a real gate violation, such as a video about to be bought for a scene\n  whose assets are not locked.\n\n## The project record\n\nThe film's state is one record, and it outranks your memory of it. Where the host gives you\nfiles, keep it as `film.json` in the working folder; otherwise keep it in the conversation and\ngive it to the user once, at the end of a working session, to paste back next time. Never print it\nmid-flow. Update it whole at every milestone: a gate passed, an asset locked, a batch dispatched or\nlanded, a review round, picture lock, the export. Its shape is `references/project-record.md`.\n\nBeside the facts it keeps the **brief**: the logline, the world in three sentences, the people as\npeople, and the standing decisions with their reasons (\"hard cuts only: the film is about\nabruptness\"). On resume, read it before saying where things stand. With no record at hand, take\nwhat the user says about the film as its state and carry on; ask for the record only when the step\nneeds a fact they have not given.\n\n## Gates\n\n**A gate is passed only when its checklist in `references/stages.md` is met**, or when the user\nconsciously overrides it; record the override and its reason. Before you say a stage is done or\nname the next one, write its checklist with ✓ or ✗ per line and the evidence beside each ✓ (a\nstatus a tool returned, a user's yes, a recorded override). A line with ✗ means the stage is not\ndone: say which line and what closes it.\n\n**Choosing how to meet a rule is your craft call; choosing to spend or risk money against a closed\ngate is never yours.** Which model shortlist, which order, whether a face needs one more view: yours,\nrecorded, never asked. Buying video for a scene whose assets are not locked, going beyond a quote,\ntrading quality for money: the user's.\n\n**The challenger at each decision.** Before you go on from a decision, quality-review's challenger (the\n`challenger` agent where the host has it) asks \"why this?\" of it: the idea (stage 1), the look and\nthe story (2, 3), the shot list (4), each sheet, plate, scene picture and panel picked and why (5, 6), and\nevery quote before its SPEND (5, 6, 7, 9, and a repair in 8 that needs a generation). Act on its\nverdict as quality-review says. A `stop`, or a `rethink` of the user's own choice, goes to the user in the\nnext ASK, the cheaper alternative first, before anything is spent.\n\n## 1. The idea\n\n- **Read the user's brief first.** Every file in the material that is not media, read in full\n  before the first question, as picsart-video-rules's The user's own brief says. A brief sets the message, the\n  audience and the must-shows.\n\nAsk for the idea only if the user has not given one. Once there is one, ask nothing more here:\nruntime and frame are set on the look console, and the story proposes an ending the user can\nchange.\n\n## 2. The look\n\n**`picsart_film_setup` comes first, before a word of story is written**, one call per visual\nworld. Genre decides how the story is told, and every shot card sits under what this console\nlocks: the style line, the lens family the cards' focal lengths come from, and the colour scheme\neach card's own palette has to fit.\n\n- Pre-set it from the idea with `suggested`, one `suggested.why` line each, as film-story-writing says: the genre the\n  events make, a tone when the story names a period, and the colour.\n- **`film` (the title) is required.** `ratio` and `duration` go inside `suggested.selections`, under\n  those field names, never as top-level arguments: the schema rejects anything it does not list.\n- **Pass `ratio` whenever the user named a format at all** (\"vertical\", \"TikTok\", \"square\"). Pass\n  the runtime they said as `duration`. Nothing infers a format; the console's default stands\n  otherwise.\n- The console is the ASK. On `film_setup_feedback` (`verdict: \"locked\"`), store `stylePrefix`\n  verbatim and the `selections` as they came. That lock is the look's lock; there is no later one.\n- If the genre changes at any point, film-story-writing rewrites the story first.\n\n## 3. The story and the model\n\n**The story.** film-story-writing writes it, for the locked genre, with its viewer track. State the identity budget\nyou inferred (\"two faces and one garage\") rather than asking for it. Show the track's after-watch questions under the\nstory, for correction: they are what the user and the cold watch are asked after each draft.\n\n**The model, in the same turn.** The candidates are the current models, in this order:\n\n| Model | Frame | Length per run | Reference images | Draft |\n|---|---|---|---|---|\n| `seedance-2.5` | 16:9, 9:16, 1:1, 4:3, 3:4, 21:9 | 4–30 s | 30 | `draft: true` |\n| `kling-v4-omni` | 16:9, 9:16, 1:1, 21:9 | 3–30 s | 8 | none: `720p` |\n| `wan-3.0-video` | 16:9, 9:16, 1:1, 4:3, 3:4 | 2–30 s | 10 | none: `480P` |\n| `veo-3.1` | 16:9, 9:16 | 4, 6 or 8 s | 3 | none: `720p` |\n\nRead each one's `picsart_model_params` before the board (film-shot-generation's model steps 2 and\n3); the table is a guide, the params decide. Drop a candidate only when its params cannot hold the\nfilm's frame or its runs (Veo 3.1 holds no 1:1 and no run over 8 s). Never offer an older model\n(Seedance 2.0, its Fast and Mini, Kling V3, Hailuo, Wan 2.7) unless the user names it. The user's\nbalance and the cheapest-first rule set the draft resolution, never the model: they never put an\nolder model on the board or make one `recommended`.\n\nOpen `picsart_model_choose` under the story with the candidates that survive, in that order, the\nfirst one `candidates[].recommended`, each `candidates[].bestFor` line written as this film's trade\n(\"one continuous 30 s take, tops out at 720p\").\n\n- The pick is the story's yes unless the user sends a note with it. A note about what happens is\n  answered as film-story-writing says, and the rewritten paragraph is shown again with the model board.\n- On the pick, record the model, its take ceiling and its edit and extend siblings, as film-shot-generation\n  finds them. One model for the whole film. A Seedance pick (`seedance-…`) also brings in the `sd25-pe`\n  skill for Seedance 2.5 or `sd2-pe` for Seedance 2.0, as film-shot-generation's Seedance reference says.\n\n## 4. The shot list\n\n**`picsart_film_shotlist` once, with every scene in one call.** Load film-story-writing before you write\nthe cards: it turns the approved story into them, and its peak rule marks one card, the `Peak`\nline's shot, with the moved face `unguarded` and what shows (\"@teo relief, unguarded: the tears\ncome\"), every other face held in; film-shot-generation packs them into runs against the model's ceiling, with one join\nsentence on the shot that opens each run. Pass `film`, the model, and the setup's defaults, so the\nuser never picks from a vocabulary the film has not adopted.\n\n- The board approves camera and seconds. It is not a place to rewrite the story: an edit that\n  changes what happens is a story note, so rewrite the paragraph first, then open the board again.\n- On `shotlist_board_feedback`, **replace** your list with it, runs included. Fields the board does\n  not carry (references, prompt versions, trims) stay on the shot by id.\n- A long scene held in one shot comes with film-shot-generation' coverage recommendation on its card. Keep\n  the single shot only if the user chooses it on the board.\n- A card that film-shot-generation flags for a kinetic move on a big face, set on the board or changed\n  later, gets one short ASK (with the host's own choice tool where it offers one, such as request_user_input in Codex's Plan mode, so the user taps an option; a Picsart board the step names asks there instead; only where neither works, the options numbered in one message, the recommended one first; in unattended pace, never ask: write it to the project record's openDecisions with the answer you assumed, as picsart-video-rules says) before the run is compiled: the move as the user set it, or one of\n  film-shot-generation' safer versions. The camera stays the user's.\n- After a long stretch on one video, offer once to reopen the board to recap what comes next.\n  Honour a no without asking again.\n\n## 5. Cast, places and props\n\n**The project folder first**, before anything is generated. `picsart_drive_create_folder` with\n`path: \"Picsart Films/<film-slug>\"` and\n`children: [\"Library\", \"Assets\", \"Shots\", \"Exports\"]`. Keep every uid it returns in the record.\nSay it once, plainly: \"Created Picsart Films/the-garage in your Picsart Drive, with Library,\nAssets, Shots and Exports inside. Everything this film makes is filed there.\" Never say it again,\nand never list the whole Drive: no `list` without a `folderUid`. Pass the right `folderUid` on\nevery `picsart_generate` and `picsart_job_status` call of the film, and the project folder as\n`projectFolderUid` on every asset call. A finished job is filed only when you save it, as\npicsart-video-rules's SPEND rule 4 says: save every finished picture and take into its folder before you\nshow it. Never call a filed file permanent.\n\nThen film-cast-design's conveyor, in one pass:\n\n1. Draft every descriptor as film-cast-design says, then offer the cast board once\n   (film-cast-design, *The starting point*). It is the one stop here and costs nothing; a reply that\n   ignores it keeps the story's descriptors. There is no other approval round.\n2. Compile each picture with `picsart_film_compile_prompt` (a reference `kind`) and read its\n   `check`, then **one SPEND for the whole batch**: every sheet and plate on one\n   quote.\n3. Dispatch on the yes as one batch (picsart-video-rules, SPEND), with `folderUid` set to Assets, and\n   let the batch's card follow the jobs as picsart-video-rules says.\n4. Look at each picture (picsart-video-rules, Asset URLs) before anything uses it, then put them all on\n   `picsart_film_review_assets` in one call (at most 12 tiles; more go on a second board), with the one thing to judge them by as the board's `judge`, and one line per tile as its `assets[].why`.\n5. Act on the reply as `references/board-replies.md` says. Each approved asset is cut into views and\n   locked with `picsart_film_save_asset`, as film-cast-design says. A change is regenerated under its own SPEND and put on a fresh board with `assets[].version` and\n   `assets[].previousUrl`. A discarded tile is never used.\n\nA person the user photographed is saved as it came and is not put up for approval: it is theirs.\nfilm-cast-design flags what it cannot settle on its own, about a photo the user brought or about the\nfilm's era. Raise each flag once, as one short ASK (with the host's own choice tool where it offers one, such as request_user_input in Codex's Plan mode, so the user taps an option; a Picsart board the step names asks there instead; only where neither works, the options numbered in one message, the recommended one first; in unattended pace, never ask: write it to the project record's openDecisions with the answer you assumed, as picsart-video-rules says) with the options film-cast-design names. Anything\ngenerated is its own SPEND.\n\n## 6. Storyboard and animatic\n\nThe film is drafted on stills and sound, and the user watches it before any video is bought. Load\nfilm-animatic before you say what this stage needs or ask anything in it. Its yes is the gate into\nshooting.\n\n1. **Scene pictures.** Every scene gets its pictures: the wide, the scene picture cut from it,\n   and a room map where the scene cuts between walls, as film-shot-generation says. The scene\n   picture is the scene's opening panel and the opening frame of its first run.\n2. **One panel per shot**, compiled from its card and checked against its scene picture, as\n   film-animatic says. A real app's screen in a shot is built as a scene layer from the user's\n   own screenshots or recording, never generated. **One SPEND (quote it in one line, then get the yes as an ASK with \"Yes, go ahead\" / \"Yes, up to N credits for this task\" / \"No\": the host's own choice tool where it offers one, otherwise those options numbered in one message; the host's own confirmation before a tool runs is not this yes; unless a spend limit the user stated covers it: N credits or an explicit no-limit (\"as much as needed\"), never inferred from words like \"go ahead\". Within it, ask nothing: quote it in one line (\"About 8 credits; 12 of 20 left after this\"), call it, then say what it spent and what remains, keeping a running total that includes failed calls, and stop to ask before the first call that would cross it. A money amount is asked once to restate it in credits; in unattended pace, never ask: call only with a consent or a stated spend limit already recorded, otherwise write the quote to pendingSpends and stop, as picsart-video-rules says) for every scene picture and\n   panel**, batched as picsart-video-rules says (at most 10 a call), and\n   `picsart_film_review_assets` for all of them, 12 tiles a board.\n3. **The sound**: every line in its person's voice, a bed per scene and the card's effects, as\n   film-animatic says, on one SPEND (quote it in one line, then get the yes as an ASK with \"Yes, go ahead\" / \"Yes, up to N credits for this task\" / \"No\": the host's own choice tool where it offers one, otherwise those options numbered in one message; the host's own confirmation before a tool runs is not this yes; unless a spend limit the user stated covers it: N credits or an explicit no-limit (\"as much as needed\"), never inferred from words like \"go ahead\". Within it, ask nothing: quote it in one line (\"About 8 credits; 12 of 20 left after this\"), call it, then say what it spent and what remains, keeping a running total that includes failed calls, and stop to ask before the first call that would cross it. A money amount is asked once to restate it in credits; in unattended pace, never ask: call only with a consent or a stated spend limit already recorded, otherwise write the quote to pendingSpends and stop, as picsart-video-rules says), each voice line's real length probed before anything is\n   timed to it.\n4. **The animatic**: built, validated, cut-checked, looked at and watched cold as film-animatic says\n   (quality-review's cold watch, quoted first with its own SPEND (quote it in one line, then get the yes as an ASK with \"Yes, go ahead\" / \"Yes, up to N credits for this task\" / \"No\": the host's own choice tool where it offers one, otherwise those options numbered in one message; the host's own confirmation before a tool runs is not this yes; unless a spend limit the user stated covers it: N credits or an explicit no-limit (\"as much as needed\"), never inferred from words like \"go ahead\". Within it, ask nothing: quote it in one line (\"About 8 credits; 12 of 20 left after this\"), call it, then say what it spent and what remains, keeping a running total that includes failed calls, and stop to ask before the first call that would cross it. A money amount is asked once to restate it in credits; in unattended pace, never ask: call only with a consent or a stated spend limit already recorded, otherwise write the quote to pendingSpends and stop, as picsart-video-rules says) unless every call is quoted at\n   0 credits), then REVIEWed in the scene editor,\n   with its sound, opened cold. Notes route as film-animatic says: a story note\n   goes back to stage 3's paragraph, a shot note to that panel or line alone, each change made\n   again under its own SPEND. Loop until the user says yes.\n\n**No still test.** The scene pictures are where the cast is checked, as film-cast-design says, and\nso are the panels: say in their review what you saw in each face. A change to a person or a prop goes back\nthrough stage 5's conveyor alone, under its own SPEND, on a fresh board.\n\n**The gate into shooting:** the animatic approved, film-cast-design's gate into a run held for every\nrun, and every scene it spans with approved pictures. A user who wants to shoot without the\nanimatic may, as a recorded override; never skip it yourself.\n\n## 7. Shooting\n\n**Which shots go to video is the user's.** ASK (with the host's own choice tool where it offers one, such as request_user_input in Codex's Plan mode, so the user taps an option; a Picsart board the step names asks there instead; only where neither works, the options numbered in one message, the recommended one first; in unattended pace, never ask: write it to the project record's openDecisions with the answer you assumed, as picsart-video-rules says) once, all shots recommended unless the\nanimatic showed a held panel works as it is; a shot kept as a panel stays in the cut as approved.\nQuote only the picked shots, each opening on its approved panel, as film-animatic says.\n\nBefore any run is quoted, a shot that film-shot-generation flags for a palette arguing with the film's\nscheme gets one short ASK (with the host's own choice tool where it offers one, such as request_user_input in Codex's Plan mode, so the user taps an option; a Picsart board the step names asks there instead; only where neither works, the options numbered in one message, the recommended one first; in unattended pace, never ask: write it to the project record's openDecisions with the answer you assumed, as picsart-video-rules says) with its options.\n\n1. **The forecast, once, before the first video:** runs × each run's seconds at the model's draft\n   rate from `picsart_preflight`, plus a margin for repairs, and the finish beside it. It is an\n   estimate, not a quote.\n2. **Shoot every run as a draft, in one batch**, as film-shot-generation says: the model's draft\n   setting or its lowest resolution, and no test run first. Every independent run is compiled,\n   verified and sent together, one call per run: one quote for the batch with the finish priced\n   beside it as an estimate, one yes, one monitor. The yes buys the drafts only. A run that waits for an earlier take (its frames\n   are the references) is its own SPEND once that take lands and passes your check.\n3. **No film so far.** While takes run, never assemble, cut, open or show the film so far: a landed\n   take waits for the others. As each take lands, find its actual cuts and judge it as\n   film-shot-generation's takes reference says. That is your technical check, not acceptance:\n   every take stays a candidate until the user approves the cut (8). No question between the\n   takes and the cut.\n4. Dialogue is judged in the cut's REVIEW, by ear. Say that the words were not checked against the\n   script by a tool.\n\nShooting is done when every take has landed and passed your check, with its actual cuts, prompt,\nquote and handle in the record. No take is accepted yet.\n\n## 8. The cut\n\nWhen the last take lands, film-cutting assembles the film once: every candidate take in story order\nwith hard cuts, every generation one clip exactly as generated: no split at a run's internal cuts,\nno trims, no transitions, padding or freeze frames. The user's own trims and splits are kept and\nnever recomputed. Check it with quality-review, its cold watch included (quoted first with its own SPEND (quote it in one line, then get the yes as an ASK with \"Yes, go ahead\" / \"Yes, up to N credits for this task\" / \"No\": the host's own choice tool where it offers one, otherwise those options numbered in one message; the host's own confirmation before a tool runs is not this yes; unless a spend limit the user stated covers it: N credits or an explicit no-limit (\"as much as needed\"), never inferred from words like \"go ahead\". Within it, ask nothing: quote it in one line (\"About 8 credits; 12 of 20 left after this\"), call it, then say what it spent and what remains, keeping a running total that includes failed calls, and stop to ask before the first call that would cross it. A money amount is asked once to restate it in credits; in unattended pace, never ask: call only with a consent or a stated spend limit already recorded, otherwise write the quote to pendingSpends and stop, as picsart-video-rules says) unless\nevery call is quoted at 0 credits; on a no, the review line says \"no cold watch yet\"), then REVIEW the whole cut, unasked and opened cold: this is the film's review. Once the user has\nanswered, say what your check observed in each take. **The user's approval of the cut\naccepts every take in it**, and its shots become `final`.\n\n**Notes route by meaning**, as film-shot-generation says: an edit, an extend or a re-roll. A note it\nflags as ambiguous gets one short ASK (with the host's own choice tool where it offers one, such as request_user_input in Codex's Plan mode, so the user taps an option; a Picsart board the step names asks there instead; only where neither works, the options numbered in one message, the recommended one first; in unattended pace, never ask: write it to the project record's openDecisions with the answer you assumed, as picsart-video-rules says) between its two routes. **Each is its own SPEND**, shot as a draft\nlike the takes: a yes to a run is not a yes to its repair. A note on a seam is not a licence to buy footage: film-cutting's\njoin repair diagnoses first. A bridge between two runs is its own SPEND too, reviewed as\nfilm-cutting's join repair says. Apply what the user points at, re-cut once and open it again, until\nthey call it final. After that, change no picture unless they ask.\n\n## 9. Finishing\n\nIn this order, as film-finishing says: the finish of the draft takes, then colour, then sound.\n\n1. **Finish the approved cut**, as film-finishing says: from each draft's `finalizeDraft` handle\n   where it has one, otherwise an upscale or the approved run generated again at the finish\n   settings. It is its own SPEND (quote it in one line, then get the yes as an ASK with \"Yes, go ahead\" / \"Yes, up to N credits for this task\" / \"No\": the host's own choice tool where it offers one, otherwise those options numbered in one message; the host's own confirmation before a tool runs is not this yes; unless a spend limit the user stated covers it: N credits or an explicit no-limit (\"as much as needed\"), never inferred from words like \"go ahead\". Within it, ask nothing: quote it in one line (\"About 8 credits; 12 of 20 left after this\"), call it, then say what it spent and what remains, keeping a running total that includes failed calls, and stop to ask before the first call that would cross it. A money amount is asked once to restate it in credits; in unattended pace, never ask: call only with a consent or a stated spend limit already recorded, otherwise write the quote to pendingSpends and stop, as picsart-video-rules says), after the cut is approved, asked as film-finishing's one\n   question: finish the approved takes, or keep the drafts. Then the cut is re-assembled at the\n   finish size with the user's trims.\n2. **Colour:** ASK (with the host's own choice tool where it offers one, such as request_user_input in Codex's Plan mode, so the user taps an option; a Picsart board the step names asks there instead; only where neither works, the options numbered in one message, the recommended one first; in unattended pace, never ask: write it to the project record's openDecisions with the answer you assumed, as picsart-video-rules says) with three or four looks that suit the film, from the look list in\n   `picsart_scene_capabilities` (`sections: [\"looksCompact\"]`). Applying one is free.\n   When the takes look glossy or plastic, as generated footage often does, one option is the\n   realism grade, applied as the realistic-color-grade skill says.\n3. **Music:** offer it once, only after the cut is final, and never bare: ASK (with the host's own choice tool where it offers one, such as request_user_input in Codex's Plan mode, so the user taps an option; a Picsart board the step names asks there instead; only where neither works, the options numbered in one message, the recommended one first; in unattended pace, never ask: write it to the project record's openDecisions with the answer you assumed, as picsart-video-rules says) with the brief\n   drafted as the background-music skill says, and three exits: generate it, change the brief, or skip. A\n   changed brief is redrafted and asked again; a skip is settled for the session. A yes is a SPEND,\n   as picsart-video-rules says. Lay the bed as film-finishing says, then REVIEW the film with it, on how it\n   sits under the dialogue. A note on its level moves it as the background-music skill says; a different\n   track goes back through the background-music skill's brief, with a new SPEND. A film going to festivals\n   or dubbing gets film-finishing's sound-team handoff offered once.\n\n## 10. Deliver\n\nDELIVER the final cut once, as picsart-video-rules says. Any further master from film-finishing's delivery\nlist is confirmed with one ASK before the first is exported. A master in another shape is reframed as the\nfootage-reframing skill says.\nThen film-finishing's archive and disclosure: give the user the disclosure text (every model used,\nper stage) and record it, and say generated music's licence is theirs to check before a festival or\na commercial use.\n\n## When something fails\n\n- **Out of credits: zero retries.** Say which step is paused and what it needs against the balance\n  `picsart_credits` reads. Keep the record and every job handle. Continue only when the user says\n  their credits are there; never poll the balance.\n- **A dropped call is not a failed generation**: follow its job as film-shot-generation says.\n- **A board that errors on a value** gets the value fixed and the board sent again. A board the\n  host cannot draw gets the host notes' fallback, and the gate still holds.\n- **Anything else a stage cannot run without** gets one identical retry, then one plain line: what\n  you tried, what blocked it, what you need. Never reword and refire.\n- **An outage is status, not a decision.** Keep going on everything free, keep the blocked item in\n  `openDecisions`, and try again next turn. Never offer a choice the rules already answer, such as\n  giving up a lead's consistency to dodge a temporary outage.\n"
AFTER
"---\nname: movie-producer\ndescription: Make a short narrative film from a story, with recurring characters, one look and approved cast/location references, then draft video and a reviewed cut. Storyboard or animatic only on explicit request. Use for short films, movies, multi-scene scripts, or continuing an existing film (shot list, shot changes or next step). Load first; it brings in the film skills for each stage. Not for a drama series or its episodes (make-short-drama), a single clip, or footage the user already has.\nmetadata:\n  uses: film-story-writing, film-cast-design, film-shot-generation, film-cutting, film-finishing, footage-reframing, background-music, scene-building-basics, quality-review, realistic-color-grade, sd25-pe, sd2-pe, film-animatic, voice-over-generation\n  optional: realistic-color-grade, film-animatic, voice-over-generation\n  title: Produce a short film\n  short-description: Make a short film from your story, scene by scene\n  argument-hint: '[story idea or script]'\n  starter-prompt: Make a short film from my story.\n---\n\n# Short film\n\nA film is not a long video. The model has no memory between generations: describe a character\nloosely and he arrives in every shot with a different face, jacket and age. Everything here exists\nto keep those people and places consistent. Lock the story, shot list, cast and location references,\nthen shoot draft video directly. The first moving draft the user reviews is the assembled cut.\nStoryboard panels and an animatic are made only when the user explicitly requests them. They are\nnot part of the default flow, and are never offered as another decision before shooting.\n\nRead picsart-video-rules first. One job: a story in, a short film out, with recurring people and places\nand one look.\n\nBefore acting on a stage, load the skills in its row that apply to this job, also when the work resumes there.\n`(preview-requested)` applies only to an explicit request for a storyboard or animatic;\n`(animatic-requested)` only to an explicit animatic request. These skills and the preview REVIEW\nare otherwise skipped; the location references are still prepared.\n\n| Stage | Gate | Skills |\n|---|---|---|\n| 1. The idea | — | — |\n| 2. The look | ASK | film-story-writing |\n| 3. The story and the model | ASK | film-story-writing, film-shot-generation, sd2-pe, sd25-pe |\n| 4. The shot list | ASK | film-story-writing, film-shot-generation |\n| 5. Cast, places and props | SPEND, ASK, REVIEW (preview-requested) | film-cast-design, film-shot-generation, scene-building-basics, film-animatic (preview-requested), voice-over-generation (animatic-requested), quality-review (preview-requested) |\n| 6. Shooting | SPEND, ASK | film-shot-generation |\n| 7. The cut | SPEND, ASK, REVIEW | film-cutting, scene-building-basics, quality-review |\n| 8. Finishing | SPEND, ASK, REVIEW | film-finishing, background-music, realistic-color-grade |\n| 9. Deliver | ASK, DELIVER | film-finishing, footage-reframing |\n\nRead these before you need them:\n\n| File | Read it before you… |\n|---|---|\n| `references/stages.md` | say a stage is done, or open the next one |\n| `references/board-replies.md` | act on a reply from any board |\n| `references/project-record.md` | write or resume the project record |\n\n## Before you start\n\n**Route first.** The dividing line is recurring identity across scenes.\n\n| The user brings | Route |\n|---|---|\n| One clip's worth of idea (\"a boot stepping onto scree\") | Not this use case. Say so, and offer one generation: `picsart_model_choose`, then SPEND (quote it in one line, then get the yes as an ASK with \"Yes, go ahead\" / \"Yes, up to N credits for this task\" / \"No\": the host's own choice tool where it offers one, otherwise those options numbered in one message; the host's own confirmation before a tool runs is not this yes; unless a spend limit the user stated covers it: N credits or an explicit no-limit (\"as much as needed\"), never inferred from words like \"go ahead\". Within it, ask nothing: quote it in one line (\"About 8 credits; 12 of 20 left after this\"), call it, then say what it spent and what remains, keeping a running total that includes failed calls, and stop to ask before the first call that would cross it. A money amount is asked once to restate it in credits; in unattended pace, never ask: call only with a consent or a stated spend limit already recorded, otherwise write the quote to pendingSpends and stop, as picsart-video-rules says) and `picsart_generate` |\n| Footage to cut together | Not this use case. Say it is not built yet here |\n| A story: scenes, people who recur, dialogue | This use case, from stage 1 |\n| A film already under way (a project record) | Resume: read the record, say where the film stands, continue at its stage |\n\n**Pace: director by default**, as picsart-video-rules says. In express pace the user comes in only for the\nboards, the three locks (the look, the story with its model, the assets), the cut's review, every charged call no stated spend limit covers and\nanything beyond a quote.\n\n## How you talk to the user\n\nTalk and ask as picsart-video-rules says. Here that means:\n\n- one board per decision; everything else waits in the record's `openDecisions`;\n- what each board's reply holds is in `references/board-replies.md`;\n- where things stand reads like \"Stage 5 of 9 · cast, places and props — locking Cal (2 of 5\n  done)\", and the gate view shows which scenes have everything they need (\"not ready yet\", never\n  \"a hole\");\n- an alarm word is for a real gate violation, such as a video about to be bought for a scene\n  whose assets are not locked.\n\n## The project record\n\nThe film's state is one record, and it outranks your memory of it. Where the host gives you\nfiles, keep it as `film.json` in the working folder; otherwise keep it in the conversation and\ngive it to the user once, at the end of a working session, to paste back next time. Never print it\nmid-flow. Update it whole at every milestone: a gate passed, an asset locked, a batch dispatched or\nlanded, a review round, picture lock, the export. Its shape and the migration of older ten-stage records are in `references/project-record.md`.\n\nBeside the facts it keeps the **brief**: the logline, the world in three sentences, the people as\npeople, and the standing decisions with their reasons (\"hard cuts only: the film is about\nabruptness\"). On resume, read it before saying where things stand. With no record at hand, take\nwhat the user says about the film as its state and carry on; ask for the record only when the step\nneeds a fact they have not given.\n\n## Gates\n\n**A gate is passed only when its checklist in `references/stages.md` is met**, or when the user\nconsciously overrides it; record the override and its reason. Before you say a stage is done or\nname the next one, write its checklist with ✓ or ✗ per line and the evidence beside each ✓ (a\nstatus a tool returned, a user's yes, a recorded override). A line with ✗ means the stage is not\ndone: say which line and what closes it.\n\n**Choosing how to meet a rule is your craft call; choosing to spend or risk money against a closed\ngate is never yours.** Which model shortlist, which order, whether a face needs one more view: yours,\nrecorded, never asked. Buying video for a scene whose assets are not locked, going beyond a quote,\ntrading quality for money: the user's.\n\n**The challenger at each decision.** Before you go on from a decision, quality-review's challenger (the\n`challenger` agent where the host has it) asks \"why this?\" of it: the idea (stage 1), the look and\nthe story (2, 3), the shot list (4), each sheet, plate, scene picture and location map picked and why (5), and\nevery quote before its SPEND (5, 6, 8, and a repair in 7 that needs a generation). Act on its\nverdict as quality-review says. A `stop`, or a `rethink` of the user's own choice, goes to the user in the\nnext ASK, the cheaper alternative first, before anything is spent.\n\n## 1. The idea\n\n- **Read the user's brief first.** Every file in the material that is not media, read in full\n  before the first question, as picsart-video-rules's The user's own brief says. A brief sets the message, the\n  audience and the must-shows.\n\nAsk for the idea only if the user has not given one. Once there is one, ask nothing more here:\nruntime and frame are set on the look console, and the story proposes an ending the user can\nchange.\n\n## 2. The look\n\n**`picsart_film_setup` comes first, before a word of story is written**, one call per visual\nworld. Genre decides how the story is told, and every shot card sits under what this console\nlocks: the style line, the lens family the cards' focal lengths come from, and the colour scheme\neach card's own palette has to fit.\n\n- Pre-set it from the idea with `suggested`, one `suggested.why` line each, as film-story-writing says: the genre the\n  events make, a tone when the story names a period, and the colour.\n- **`film` (the title) is required.** `ratio` and `duration` go inside `suggested.selections`, under\n  those field names, never as top-level arguments: the schema rejects anything it does not list.\n- **Pass `ratio` whenever the user named a format at all** (\"vertical\", \"TikTok\", \"square\"). Pass\n  the runtime they said as `duration`. Nothing infers a format; the console's default stands\n  otherwise.\n- The console is the ASK. On `film_setup_feedback` (`verdict: \"locked\"`), store `stylePrefix`\n  verbatim and the `selections` as they came. That lock is the look's lock; there is no later one.\n- If the genre changes at any point, film-story-writing rewrites the story first.\n\n## 3. The story and the model\n\n**The story.** film-story-writing writes it, for the locked genre, with its viewer track. State the identity budget\nyou inferred (\"two faces and one garage\") rather than asking for it. Show the track's after-watch questions under the\nstory, for correction: they are what the user and the cold watch are asked after each draft.\n\n**The model, in the same turn.** The candidates are the current models, in this order:\n\n| Model | Frame | Length per run | Reference images | Draft |\n|---|---|---|---|---|\n| `seedance-2.5` | 16:9, 9:16, 1:1, 4:3, 3:4, 21:9 | 4–30 s | 30 | `draft: true` |\n| `kling-v4-omni` | 16:9, 9:16, 1:1, 21:9 | 3–30 s | 8 | none: `720p` |\n| `wan-3.0-video` | 16:9, 9:16, 1:1, 4:3, 3:4 | 2–30 s | 10 | none: `480P` |\n| `veo-3.1` | 16:9, 9:16 | 4, 6 or 8 s | 3 | none: `720p` |\n\nRead each one's `picsart_model_params` before the board (film-shot-generation's model steps 2 and\n3); the table is a guide, the params decide. Drop a candidate only when its params cannot hold the\nfilm's frame or its runs (Veo 3.1 holds no 1:1 and no run over 8 s). Never offer an older model\n(Seedance 2.0, its Fast and Mini, Kling V3, Hailuo, Wan 2.7) unless the user names it. The user's\nbalance and the cheapest-first rule set the draft resolution, never the model: they never put an\nolder model on the board or make one `recommended`.\n\nOpen `picsart_model_choose` under the story with the candidates that survive, in that order, the\nfirst one `candidates[].recommended`, each `candidates[].bestFor` line written as this film's trade\n(\"one continuous 30 s take, tops out at 720p\").\n\n- The pick is the story's yes unless the user sends a note with it. A note about what happens is\n  answered as film-story-writing says, and the rewritten paragraph is shown again with the model board.\n- On the pick, record the model, its take ceiling and its edit and extend siblings, as film-shot-generation\n  finds them. One model for the whole film. A Seedance pick (`seedance-…`) also brings in the `sd25-pe`\n  skill for Seedance 2.5 or `sd2-pe` for Seedance 2.0, as film-shot-generation's Seedance reference says.\n\n## 4. The shot list\n\n**`picsart_film_shotlist` once, with every scene in one call.** Load film-story-writing before you write\nthe cards: it turns the approved story into them, and its peak rule marks one card, the `Peak`\nline's shot, with the moved face `unguarded` and what shows (\"@teo relief, unguarded: the tears\ncome\"), every other face held in; film-shot-generation packs them into runs against the model's ceiling, with one join\nsentence on the shot that opens each run. Pass `film`, the model, and the setup's defaults, so the\nuser never picks from a vocabulary the film has not adopted.\n\n**Use the model's capacity before opening the board.** Load film-shot-generation's Runs method\nand its seams reference. Read the selected model's accepted durations and reference limits from\n`picsart_model_params`, then pack the ordered shot cards into the fewest runs that fit, across\nscene boundaries. Assign run ids only after packing: the board preserves those boundaries, so\none id per beat would lock in needless generations. Several cuts belong inside one generation;\na climax, a close-up, a new scene or \"easier to generate\" is no reason to split it.\n\nCheck each boundary: can the next shot fit in the preceding run within the model's duration and\nreference limits? If yes, keep packing; if no, record the limiting constraint. Preserve shot order,\nshot lengths and dialogue; do not stretch shots or add filler to reach the ceiling. The final\nremainder can be short. A shorter run otherwise needs a specific model limit or the user's explicit\nsplit. For example, six proposed runs of 7, 7, 4, 3, 6 and 3 seconds become one 30-second generation\nwhen the selected model accepts 30 seconds and their combined references fit. The nine shot\ncards and their internal cuts stay separate inside that generation.\n\nWrite the internal cut pairs and each necessary run edge using film-shot-generation's seams\nreference: match action, eyelines and screen direction, keep geography, and carry frames only\nfor its named exceptions. Fewer generations must preserve this method, not replace the cuts\nwith one long shot or buy a bridge for every boundary.\n\n- The board approves camera and seconds. It is not a place to rewrite the story: an edit that\n  changes what happens is a story note, so rewrite the paragraph first, then open the board again.\n- On `shotlist_board_feedback`, **replace** your list with it, runs included. Fields the board does\n  not carry (references, prompt versions, trims) stay on the shot by id.\n- A long scene held in one shot comes with film-shot-generation' coverage recommendation on its card. Keep\n  the single shot only if the user chooses it on the board.\n- A card that film-shot-generation flags for a kinetic move on a big face, set on the board or changed\n  later, gets one short ASK (with the host's own choice tool where it offers one, such as request_user_input in Codex's Plan mode, so the user taps an option; a Picsart board the step names asks there instead; only where neither works, the options numbered in one message, the recommended one first; in unattended pace, never ask: write it to the project record's openDecisions with the answer you assumed, as picsart-video-rules says) before the run is compiled: the move as the user set it, or one of\n  film-shot-generation' safer versions. The camera stays the user's.\n- After a long stretch on one video, offer once to reopen the board to recap what comes next.\n  Honour a no without asking again.\n\n## 5. Cast, places and props\n\n**The project folder first**, before anything is generated. `picsart_drive_create_folder` with\n`path: \"Picsart Films/<film-slug>\"` and\n`children: [\"Library\", \"Assets\", \"Shots\", \"Exports\"]`. Keep every uid it returns in the record.\nSay it once, plainly: \"Created Picsart Films/the-garage in your Picsart Drive, with Library,\nAssets, Shots and Exports inside. Everything this film makes is filed there.\" Never say it again,\nand never list the whole Drive: no `list` without a `folderUid`. Pass the right `folderUid` on\nevery `picsart_generate` and `picsart_job_status` call of the film, and the project folder as\n`projectFolderUid` on every asset call. A finished job is filed only when you save it, as\npicsart-video-rules's SPEND rule 4 says: save every finished picture and take into its folder before you\nshow it. Never call a filed file permanent.\n\nThen film-cast-design's conveyor, in one pass:\n\n1. Draft every descriptor as film-cast-design says, then offer the cast board once\n   (film-cast-design, *The starting point*). It is the one stop here and costs nothing; a reply that\n   ignores it keeps the story's descriptors. There is no other approval round.\n2. Compile each picture with `picsart_film_compile_prompt` (a reference `kind`) and read its\n   `check`, then **one SPEND for the whole batch**: every sheet and plate on one\n   quote.\n3. Dispatch on the yes as one batch (picsart-video-rules, SPEND), with `folderUid` set to Assets, and\n   let the batch's card follow the jobs as picsart-video-rules says.\n4. Look at each picture (picsart-video-rules, Asset URLs) before anything uses it, then put them all on\n   `picsart_film_review_assets` in one call (at most 12 tiles; more go on a second board), with the one thing to judge them by as the board's `judge`, and one line per tile as its `assets[].why`.\n5. Act on the reply as `references/board-replies.md` says. Each approved asset is cut into views and\n   locked with `picsart_film_save_asset`, as film-cast-design says. Before regenerating a rejected\n   picture, save that version as `rejected` and record it as below. The replacement is regenerated\n   under its own SPEND and shown alone on a fresh board, with `assets[].version`; omit `assets[].previousUrl` when the previous picture\n   was rejected. A discarded tile is recorded as rejected and never used.\n\nA person the user photographed is saved as it came and is not put up for approval: it is theirs.\nfilm-cast-design flags what it cannot settle on its own, about a photo the user brought or about the\nfilm's era. Raise each flag once, as one short ASK (with the host's own choice tool where it offers one, such as request_user_input in Codex's Plan mode, so the user taps an option; a Picsart board the step names asks there instead; only where neither works, the options numbered in one message, the recommended one first; in unattended pace, never ask: write it to the project record's openDecisions with the answer you assumed, as picsart-video-rules says) with the options film-cast-design names. Anything\ngenerated is its own SPEND.\n\n### A rejected cast picture\n\nTreat \"Change one\", \"not her\", \"profile is not ok\", \"it's not her\", or any no to a cast picture\nas a rejection. If several pictures were shown and the target is unclear, ASK (with the host's own choice tool where it offers one, such as request_user_input in Codex's Plan mode, so the user taps an option; a Picsart board the step names asks there instead; only where neither works, the options numbered in one message, the recommended one first; in unattended pace, never ask: write it to the project record's openDecisions with the answer you assumed, as picsart-video-rules says) which one\nwithout showing them again; do not regenerate until it is identified.\n\nBefore regenerating, call `picsart_film_save_asset` for the rejected version with `status: \"rejected\"`,\nits original `tag`, `sheetVersion`, `portraitUrl`, `projectFolderUid` and saved asset metadata.\nPass the saved `identityReferences` too. Every new save supplies the user's original photo URLs\nthere, or `identityReferences: []` when all views are generated. Do not infer provenance from a\nview's position; preserve unknown provenance on older records.\nRecord its tag, version, file uid, URL and all extracted view/panel URLs in the project's\n`rejectedAssets[]`, and mark that version's asset row `rejected`. Confirm the save succeeded before\na replacement is generated; on failure keep the local rejected entry and retry the save, never reuse it.\nA replacement gets a new version and stays in review until the user approves it.\n\nNever show a rejected picture again, including in a comparison, `previousUrl`, an old plan card or\nan asset recap. Never pass any part of it as a reference: no full-body front, profile, crop, view\nor panel. Rejecting one view rejects the whole sheet unless the user explicitly said otherwise;\nrecord any such exception and keep only the explicitly permitted view separate from the rejected sheet.\nCheck `rejectedAssets[]` before every display, reference selection, plan and resumed film turn.\nRemove rejected references from pending opening frames and shot plans before continuing.\n\nFor a person made from the user's own photos, keep those original photos in `identityReferences[]`\nand use them as the identity reference for every replacement. Rejecting a generated sheet never\nrejects the user's original photos; do not substitute a rejected generated face for them.\n\n### Location references before shooting\n\nKeep the location map. Follow film-shot-generation's scene-pictures reference: a wide for every\nscene, its opening scene picture cut from that wide, and a room map where the scene cuts between\nwalls. Reuse one map per place and time of day; a single outdoor background uses its wide as its\ngeography. Record the URLs in `scenes[].pictures` and the geography line in `scenes[].geography`.\n\nCompile and verify the required pictures, quote them together with SPEND (quote it in one line, then get the yes as an ASK with \"Yes, go ahead\" / \"Yes, up to N credits for this task\" / \"No\": the host's own choice tool where it offers one, otherwise those options numbered in one message; the host's own confirmation before a tool runs is not this yes; unless a spend limit the user stated covers it: N credits or an explicit no-limit (\"as much as needed\"), never inferred from words like \"go ahead\". Within it, ask nothing: quote it in one line (\"About 8 credits; 12 of 20 left after this\"), call it, then say what it spent and what remains, keeping a running total that includes failed calls, and stop to ask before the first call that would cross it. A money amount is asked once to restate it in credits; in unattended pace, never ask: call only with a consent or a stated spend limit already recorded, otherwise write the quote to pendingSpends and stop, as picsart-video-rules says), then generate the\nindependent pictures in a batch. Check each before its board review, including the cast's faces,\nopening positions and room geometry. Use `picsart_film_review_assets` for the location references\nand apply `references/board-replies.md`. Reuse approved pictures already in the record. A real app's\nscreen is built as a scene layer from the user's screenshots or recording, never generated.\n\n**No still test.** The scene pictures are where the cast is checked, as film-cast-design says.\nA cast or prop correction goes through that asset's conveyor only, under its own SPEND.\n\n**The gate into shooting:** the story and shot list approved, every scene in a run has approved\nlocation references, and film-cast-design's gate into a run holds for all its tags, read back from\n`picsart_film_list_assets`. The opening scene picture starts the scene's first run; later runs use\nfilm-shot-generation's continuity references. No storyboard panels, voiced slideshow or animatic\napproval is required in the default flow.\n\n### Only when the user requests a storyboard or animatic\n\nRecord the explicit request in `requestedPreview` (`kind: \"storyboard\"` or `\"animatic\"`,\n`status: \"requested\"`) and load film-animatic for that work. A request for a **storyboard** uses\nits panel method only: quote and make the requested panels, check them, and review them on\n`picsart_film_review_assets`. It does not buy voices, music or a timed animatic. A request for an\n**animatic** uses its timed-preview method and voice-over-generation for its sound; quote the\nneeded pictures and sound with SPEND (quote it in one line, then get the yes as an ASK with \"Yes, go ahead\" / \"Yes, up to N credits for this task\" / \"No\": the host's own choice tool where it offers one, otherwise those options numbered in one message; the host's own confirmation before a tool runs is not this yes; unless a spend limit the user stated covers it: N credits or an explicit no-limit (\"as much as needed\"), never inferred from words like \"go ahead\". Within it, ask nothing: quote it in one line (\"About 8 credits; 12 of 20 left after this\"), call it, then say what it spent and what remains, keeping a running total that includes failed calls, and stop to ask before the first call that would cross it. A money amount is asked once to restate it in credits; in unattended pace, never ask: call only with a consent or a stated spend limit already recorded, otherwise write the quote to pendingSpends and stop, as picsart-video-rules says), then validate, check and REVIEW the preview as that\nskill says. Reuse the approved cast and location references in either case.\n\nThe request chooses the work, not permission for an unquoted spend. Apply SPEND (quote it in one line, then get the yes as an ASK with \"Yes, go ahead\" / \"Yes, up to N credits for this task\" / \"No\": the host's own choice tool where it offers one, otherwise those options numbered in one message; the host's own confirmation before a tool runs is not this yes; unless a spend limit the user stated covers it: N credits or an explicit no-limit (\"as much as needed\"), never inferred from words like \"go ahead\". Within it, ask nothing: quote it in one line (\"About 8 credits; 12 of 20 left after this\"), call it, then say what it spent and what remains, keeping a running total that includes failed calls, and stop to ask before the first call that would cross it. A money amount is asked once to restate it in credits; in unattended pace, never ask: call only with a consent or a stated spend limit already recorded, otherwise write the quote to pendingSpends and stop, as picsart-video-rules says) to every new\ncharged operation. On approval, set `requestedPreview.status: \"approved\"` and continue to\nshooting; no second shot-selection question is added. Storyboards and animatics are never\nrequired, recommended as another gate, or created on a resume without that explicit request.\n\n## 6. Shooting\n\nShoot the approved shot list directly, respecting any explicit exclusions the user already made.\nDo not ask them to choose the shots again. Use the approved scene-opening images and continuity\nreferences as film-shot-generation says; never require one generated panel per shot.\n\n**Recheck capacity before the forecast or quote**, including on resume. Reconcile the approved\nshot cards, current model limits and planned runs; show the generation count and each run's\nseconds against the ceiling. A batch with six items is still six generations. Do not quote\nmergeable short runs. If correcting them changes approved run boundaries, show that correction\nin the existing approval/quote step; keep the user's explicit splits, shot choices and seconds.\nRecompile the corrected runs and their joins, and replace the old quote. Never repack a submitted\nor completed job into another paid generation; keep its handle and existing footage.\n\nBefore any run is quoted, a shot that film-shot-generation flags for a palette arguing with the film's\nscheme gets one short ASK (with the host's own choice tool where it offers one, such as request_user_input in Codex's Plan mode, so the user taps an option; a Picsart board the step names asks there instead; only where neither works, the options numbered in one message, the recommended one first; in unattended pace, never ask: write it to the project record's openDecisions with the answer you assumed, as picsart-video-rules says) with its options.\n\n1. **The forecast, once, before the first video:** runs × each run's seconds at the model's draft\n   rate from `picsart_preflight`, plus a margin for repairs, and the finish beside it. It is an\n   estimate, not a quote.\n2. **Shoot every run as a draft, in one batch**, as film-shot-generation says: the model's draft\n   setting or its lowest resolution, and no test run first. Every independent run is compiled,\n   verified and sent together, one call per run: one quote for the batch with the finish priced\n   beside it as an estimate, one yes, one monitor. The yes buys the drafts only. A run that waits for an earlier take (its frames\n   are the references) is its own SPEND once that take lands and passes your check.\n3. **No film so far.** While takes run, never assemble, cut, open or show the film so far: a landed\n   take waits for the others. As each take lands, find its actual cuts and judge it as\n   film-shot-generation's takes reference says. That is your technical check, not acceptance:\n   every take stays a candidate until the user approves the cut (7). No question between the\n   takes and the cut.\n4. Dialogue is judged in the cut's REVIEW, by ear. Say that the words were not checked against the\n   script by a tool.\n\nShooting is done when every take has landed and passed your check, with its actual cuts, prompt,\nquote and handle in the record. No take is accepted yet.\n\n## 7. The cut\n\nWhen the last take lands, film-cutting assembles the film once: every candidate take in story order\nwith hard cuts, every generation one clip exactly as generated: no split at a run's internal cuts,\nno trims, no transitions, padding or freeze frames. The user's own trims and splits are kept and\nnever recomputed. Check it with quality-review, its cold watch included (quoted first with its own SPEND (quote it in one line, then get the yes as an ASK with \"Yes, go ahead\" / \"Yes, up to N credits for this task\" / \"No\": the host's own choice tool where it offers one, otherwise those options numbered in one message; the host's own confirmation before a tool runs is not this yes; unless a spend limit the user stated covers it: N credits or an explicit no-limit (\"as much as needed\"), never inferred from words like \"go ahead\". Within it, ask nothing: quote it in one line (\"About 8 credits; 12 of 20 left after this\"), call it, then say what it spent and what remains, keeping a running total that includes failed calls, and stop to ask before the first call that would cross it. A money amount is asked once to restate it in credits; in unattended pace, never ask: call only with a consent or a stated spend limit already recorded, otherwise write the quote to pendingSpends and stop, as picsart-video-rules says) unless\nevery call is quoted at 0 credits; on a no, the review line says \"no cold watch yet\"), then REVIEW the whole cut, unasked and opened cold: this is the film's review. Once the user has\nanswered, say what your check observed in each take. **The user's approval of the cut\naccepts every take in it**, and its shots become `final`.\n\n**Notes route by meaning**, as film-shot-generation says: an edit, an extend or a re-roll. A note it\nflags as ambiguous gets one short ASK (with the host's own choice tool where it offers one, such as request_user_input in Codex's Plan mode, so the user taps an option; a Picsart board the step names asks there instead; only where neither works, the options numbered in one message, the recommended one first; in unattended pace, never ask: write it to the project record's openDecisions with the answer you assumed, as picsart-video-rules says) between its two routes. **Each is its own SPEND**, shot as a draft\nlike the takes: a yes to a run is not a yes to its repair. A note on a seam is not a licence to buy footage: film-cutting's\njoin repair diagnoses first. A bridge between two runs is its own SPEND too, reviewed as\nfilm-cutting's join repair says. Apply what the user points at, re-cut once and open it again, until\nthey call it final. After that, change no picture unless they ask.\n\n## 8. Finishing\n\nIn this order, as film-finishing says: the finish of the draft takes, then colour, then sound.\n\n1. **Finish the approved cut**, as film-finishing says: from each draft's `finalizeDraft` handle\n   where it has one, otherwise an upscale or the approved run generated again at the finish\n   settings. It is its own SPEND (quote it in one line, then get the yes as an ASK with \"Yes, go ahead\" / \"Yes, up to N credits for this task\" / \"No\": the host's own choice tool where it offers one, otherwise those options numbered in one message; the host's own confirmation before a tool runs is not this yes; unless a spend limit the user stated covers it: N credits or an explicit no-limit (\"as much as needed\"), never inferred from words like \"go ahead\". Within it, ask nothing: quote it in one line (\"About 8 credits; 12 of 20 left after this\"), call it, then say what it spent and what remains, keeping a running total that includes failed calls, and stop to ask before the first call that would cross it. A money amount is asked once to restate it in credits; in unattended pace, never ask: call only with a consent or a stated spend limit already recorded, otherwise write the quote to pendingSpends and stop, as picsart-video-rules says), after the cut is approved, asked as film-finishing's one\n   question: finish the approved takes, or keep the drafts. Then the cut is re-assembled at the\n   finish size with the user's trims.\n2. **Colour:** ASK (with the host's own choice tool where it offers one, such as request_user_input in Codex's Plan mode, so the user taps an option; a Picsart board the step names asks there instead; only where neither works, the options numbered in one message, the recommended one first; in unattended pace, never ask: write it to the project record's openDecisions with the answer you assumed, as picsart-video-rules says) with three or four looks that suit the film, from the look list in\n   `picsart_scene_capabilities` (`sections: [\"looksCompact\"]`). Applying one is free.\n   When the takes look glossy or plastic, as generated footage often does, one option is the\n   realism grade, applied as the realistic-color-grade skill says.\n3. **Music:** offer it once, only after the cut is final, and never bare: ASK (with the host's own choice tool where it offers one, such as request_user_input in Codex's Plan mode, so the user taps an option; a Picsart board the step names asks there instead; only where neither works, the options numbered in one message, the recommended one first; in unattended pace, never ask: write it to the project record's openDecisions with the answer you assumed, as picsart-video-rules says) with the brief\n   drafted as the background-music skill says, and three exits: generate it, change the brief, or skip. A\n   changed brief is redrafted and asked again; a skip is settled for the session. A yes is a SPEND,\n   as picsart-video-rules says. Lay the bed as film-finishing says, then REVIEW the film with it, on how it\n   sits under the dialogue. A note on its level moves it as the background-music skill says; a different\n   track goes back through the background-music skill's brief, with a new SPEND. A film going to festivals\n   or dubbing gets film-finishing's sound-team handoff offered once.\n\n## 9. Deliver\n\nDELIVER the final cut once, as picsart-video-rules says. Any further master from film-finishing's delivery\nlist is confirmed with one ASK before the first is exported. A master in another shape is reframed as the\nfootage-reframing skill says.\nThen film-finishing's archive and disclosure: give the user the disclosure text (every model used,\nper stage) and record it, and say generated music's licence is theirs to check before a festival or\na commercial use.\n\n## When something fails\n\n- **Out of credits: zero retries.** Say which step is paused and what it needs against the balance\n  `picsart_credits` reads. Keep the record and every job handle. Continue only when the user says\n  their credits are there; never poll the balance.\n- **A dropped call is not a failed generation**: follow its job as film-shot-generation says.\n- **A board that errors on a value** gets the value fixed and the board sent again. A board the\n  host cannot draw gets the host notes' fallback, and the gate still holds.\n- **Anything else a stage cannot run without** gets one identical retry, then one plain line: what\n  you tried, what blocked it, what you need. Never reword and refire.\n- **An outage is status, not a decision.** Keep going on everything free, keep the blocked item in\n  `openDecisions`, and try again next turn. Never offer a choice the rules already answer, such as\n  giving up a lead's consistency to dodge a temporary outage.\n"
Full snapshot data
{
  "description": "Make a short narrative film from a story, with recurring characters, one look and approved cast/location references, then draft video and a reviewed cut. Storyboard or animatic only on explicit request. Use for short films, movies, multi-scene scripts, or continuing an existing film (shot list, shot changes or next step). Load first; it brings in the film skills for each stage. Not for a drama series or its episodes (make-short-drama), a single clip, or footage the user already has.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 176
    },
    {
      "relative_path": "references/board-replies.md",
      "size_in_bytes": 6328
    },
    {
      "relative_path": "references/project-record.md",
      "size_in_bytes": 9147
    },
    {
      "relative_path": "references/stages.md",
      "size_in_bytes": 8067
    }
  ],
  "name": "movie-producer",
  "skill_md_contents": "---\nname: movie-producer\ndescription: Make a short narrative film from a story, with recurring characters, one look and approved cast/location references, then draft video and a reviewed cut. Storyboard or animatic only on explicit request. Use for short films, movies, multi-scene scripts, or continuing an existing film (shot list, shot changes or next step). Load first; it brings in the film skills for each stage. Not for a drama series or its episodes (make-short-drama), a single clip, or footage the user already has.\nmetadata:\n  uses: film-story-writing, film-cast-design, film-shot-generation, film-cutting, film-finishing, footage-reframing, background-music, scene-building-basics, quality-review, realistic-color-grade, sd25-pe, sd2-pe, film-animatic, voice-over-generation\n  optional: realistic-color-grade, film-animatic, voice-over-generation\n  title: Produce a short film\n  short-description: Make a short film from your story, scene by scene\n  argument-hint: '[story idea or script]'\n  starter-prompt: Make a short film from my story.\n---\n\n# Short film\n\nA film is not a long video. The model has no memory between generations: describe a character\nloosely and he arrives in every shot with a different face, jacket and age. Everything here exists\nto keep those people and places consistent. Lock the story, shot list, cast and location references,\nthen shoot draft video directly. The first moving draft the user reviews is the assembled cut.\nStoryboard panels and an animatic are made only when the user explicitly requests them. They are\nnot part of the default flow, and are never offered as another decision before shooting.\n\nRead picsart-video-rules first. One job: a story in, a short film out, with recurring people and places\nand one look.\n\nBefore acting on a stage, load the skills in its row that apply to this job, also when the work resumes there.\n`(preview-requested)` applies only to an explicit request for a storyboard or animatic;\n`(animatic-requested)` only to an explicit animatic request. These skills and the preview REVIEW\nare otherwise skipped; the location references are still prepared.\n\n| Stage | Gate | Skills |\n|---|---|---|\n| 1. The idea | — | — |\n| 2. The look | ASK | film-story-writing |\n| 3. The story and the model | ASK | film-story-writing, film-shot-generation, sd2-pe, sd25-pe |\n| 4. The shot list | ASK | film-story-writing, film-shot-generation |\n| 5. Cast, places and props | SPEND, ASK, REVIEW (preview-requested) | film-cast-design, film-shot-generation, scene-building-basics, film-animatic (preview-requested), voice-over-generation (animatic-requested), quality-review (preview-requested) |\n| 6. Shooting | SPEND, ASK | film-shot-generation |\n| 7. The cut | SPEND, ASK, REVIEW | film-cutting, scene-building-basics, quality-review |\n| 8. Finishing | SPEND, ASK, REVIEW | film-finishing, background-music, realistic-color-grade |\n| 9. Deliver | ASK, DELIVER | film-finishing, footage-reframing |\n\nRead these before you need them:\n\n| File | Read it before you… |\n|---|---|\n| `references/stages.md` | say a stage is done, or open the next one |\n| `references/board-replies.md` | act on a reply from any board |\n| `references/project-record.md` | write or resume the project record |\n\n## Before you start\n\n**Route first.** The dividing line is recurring identity across scenes.\n\n| The user brings | Route |\n|---|---|\n| One clip's worth of idea (\"a boot stepping onto scree\") | Not this use case. Say so, and offer one generation: `picsart_model_choose`, then SPEND (quote it in one line, then get the yes as an ASK with \"Yes, go ahead\" / \"Yes, up to N credits for this task\" / \"No\": the host's own choice tool where it offers one, otherwise those options numbered in one message; the host's own confirmation before a tool runs is not this yes; unless a spend limit the user stated covers it: N credits or an explicit no-limit (\"as much as needed\"), never inferred from words like \"go ahead\". Within it, ask nothing: quote it in one line (\"About 8 credits; 12 of 20 left after this\"), call it, then say what it spent and what remains, keeping a running total that includes failed calls, and stop to ask before the first call that would cross it. A money amount is asked once to restate it in credits; in unattended pace, never ask: call only with a consent or a stated spend limit already recorded, otherwise write the quote to pendingSpends and stop, as picsart-video-rules says) and `picsart_generate` |\n| Footage to cut together | Not this use case. Say it is not built yet here |\n| A story: scenes, people who recur, dialogue | This use case, from stage 1 |\n| A film already under way (a project record) | Resume: read the record, say where the film stands, continue at its stage |\n\n**Pace: director by default**, as picsart-video-rules says. In express pace the user comes in only for the\nboards, the three locks (the look, the story with its model, the assets), the cut's review, every charged call no stated spend limit covers and\nanything beyond a quote.\n\n## How you talk to the user\n\nTalk and ask as picsart-video-rules says. Here that means:\n\n- one board per decision; everything else waits in the record's `openDecisions`;\n- what each board's reply holds is in `references/board-replies.md`;\n- where things stand reads like \"Stage 5 of 9 · cast, places and props — locking Cal (2 of 5\n  done)\", and the gate view shows which scenes have everything they need (\"not ready yet\", never\n  \"a hole\");\n- an alarm word is for a real gate violation, such as a video about to be bought for a scene\n  whose assets are not locked.\n\n## The project record\n\nThe film's state is one record, and it outranks your memory of it. Where the host gives you\nfiles, keep it as `film.json` in the working folder; otherwise keep it in the conversation and\ngive it to the user once, at the end of a working session, to paste back next time. Never print it\nmid-flow. Update it whole at every milestone: a gate passed, an asset locked, a batch dispatched or\nlanded, a review round, picture lock, the export. Its shape and the migration of older ten-stage records are in `references/project-record.md`.\n\nBeside the facts it keeps the **brief**: the logline, the world in three sentences, the people as\npeople, and the standing decisions with their reasons (\"hard cuts only: the film is about\nabruptness\"). On resume, read it before saying where things stand. With no record at hand, take\nwhat the user says about the film as its state and carry on; ask for the record only when the step\nneeds a fact they have not given.\n\n## Gates\n\n**A gate is passed only when its checklist in `references/stages.md` is met**, or when the user\nconsciously overrides it; record the override and its reason. Before you say a stage is done or\nname the next one, write its checklist with ✓ or ✗ per line and the evidence beside each ✓ (a\nstatus a tool returned, a user's yes, a recorded override). A line with ✗ means the stage is not\ndone: say which line and what closes it.\n\n**Choosing how to meet a rule is your craft call; choosing to spend or risk money against a closed\ngate is never yours.** Which model shortlist, which order, whether a face needs one more view: yours,\nrecorded, never asked. Buying video for a scene whose assets are not locked, going beyond a quote,\ntrading quality for money: the user's.\n\n**The challenger at each decision.** Before you go on from a decision, quality-review's challenger (the\n`challenger` agent where the host has it) asks \"why this?\" of it: the idea (stage 1), the look and\nthe story (2, 3), the shot list (4), each sheet, plate, scene picture and location map picked and why (5), and\nevery quote before its SPEND (5, 6, 8, and a repair in 7 that needs a generation). Act on its\nverdict as quality-review says. A `stop`, or a `rethink` of the user's own choice, goes to the user in the\nnext ASK, the cheaper alternative first, before anything is spent.\n\n## 1. The idea\n\n- **Read the user's brief first.** Every file in the material that is not media, read in full\n  before the first question, as picsart-video-rules's The user's own brief says. A brief sets the message, the\n  audience and the must-shows.\n\nAsk for the idea only if the user has not given one. Once there is one, ask nothing more here:\nruntime and frame are set on the look console, and the story proposes an ending the user can\nchange.\n\n## 2. The look\n\n**`picsart_film_setup` comes first, before a word of story is written**, one call per visual\nworld. Genre decides how the story is told, and every shot card sits under what this console\nlocks: the style line, the lens family the cards' focal lengths come from, and the colour scheme\neach card's own palette has to fit.\n\n- Pre-set it from the idea with `suggested`, one `suggested.why` line each, as film-story-writing says: the genre the\n  events make, a tone when the story names a period, and the colour.\n- **`film` (the title) is required.** `ratio` and `duration` go inside `suggested.selections`, under\n  those field names, never as top-level arguments: the schema rejects anything it does not list.\n- **Pass `ratio` whenever the user named a format at all** (\"vertical\", \"TikTok\", \"square\"). Pass\n  the runtime they said as `duration`. Nothing infers a format; the console's default stands\n  otherwise.\n- The console is the ASK. On `film_setup_feedback` (`verdict: \"locked\"`), store `stylePrefix`\n  verbatim and the `selections` as they came. That lock is the look's lock; there is no later one.\n- If the genre changes at any point, film-story-writing rewrites the story first.\n\n## 3. The story and the model\n\n**The story.** film-story-writing writes it, for the locked genre, with its viewer track. State the identity budget\nyou inferred (\"two faces and one garage\") rather than asking for it. Show the track's after-watch questions under the\nstory, for correction: they are what the user and the cold watch are asked after each draft.\n\n**The model, in the same turn.** The candidates are the current models, in this order:\n\n| Model | Frame | Length per run | Reference images | Draft |\n|---|---|---|---|---|\n| `seedance-2.5` | 16:9, 9:16, 1:1, 4:3, 3:4, 21:9 | 4–30 s | 30 | `draft: true` |\n| `kling-v4-omni` | 16:9, 9:16, 1:1, 21:9 | 3–30 s | 8 | none: `720p` |\n| `wan-3.0-video` | 16:9, 9:16, 1:1, 4:3, 3:4 | 2–30 s | 10 | none: `480P` |\n| `veo-3.1` | 16:9, 9:16 | 4, 6 or 8 s | 3 | none: `720p` |\n\nRead each one's `picsart_model_params` before the board (film-shot-generation's model steps 2 and\n3); the table is a guide, the params decide. Drop a candidate only when its params cannot hold the\nfilm's frame or its runs (Veo 3.1 holds no 1:1 and no run over 8 s). Never offer an older model\n(Seedance 2.0, its Fast and Mini, Kling V3, Hailuo, Wan 2.7) unless the user names it. The user's\nbalance and the cheapest-first rule set the draft resolution, never the model: they never put an\nolder model on the board or make one `recommended`.\n\nOpen `picsart_model_choose` under the story with the candidates that survive, in that order, the\nfirst one `candidates[].recommended`, each `candidates[].bestFor` line written as this film's trade\n(\"one continuous 30 s take, tops out at 720p\").\n\n- The pick is the story's yes unless the user sends a note with it. A note about what happens is\n  answered as film-story-writing says, and the rewritten paragraph is shown again with the model board.\n- On the pick, record the model, its take ceiling and its edit and extend siblings, as film-shot-generation\n  finds them. One model for the whole film. A Seedance pick (`seedance-…`) also brings in the `sd25-pe`\n  skill for Seedance 2.5 or `sd2-pe` for Seedance 2.0, as film-shot-generation's Seedance reference says.\n\n## 4. The shot list\n\n**`picsart_film_shotlist` once, with every scene in one call.** Load film-story-writing before you write\nthe cards: it turns the approved story into them, and its peak rule marks one card, the `Peak`\nline's shot, with the moved face `unguarded` and what shows (\"@teo relief, unguarded: the tears\ncome\"), every other face held in; film-shot-generation packs them into runs against the model's ceiling, with one join\nsentence on the shot that opens each run. Pass `film`, the model, and the setup's defaults, so the\nuser never picks from a vocabulary the film has not adopted.\n\n**Use the model's capacity before opening the board.** Load film-shot-generation's Runs method\nand its seams reference. Read the selected model's accepted durations and reference limits from\n`picsart_model_params`, then pack the ordered shot cards into the fewest runs that fit, across\nscene boundaries. Assign run ids only after packing: the board preserves those boundaries, so\none id per beat would lock in needless generations. Several cuts belong inside one generation;\na climax, a close-up, a new scene or \"easier to generate\" is no reason to split it.\n\nCheck each boundary: can the next shot fit in the preceding run within the model's duration and\nreference limits? If yes, keep packing; if no, record the limiting constraint. Preserve shot order,\nshot lengths and dialogue; do not stretch shots or add filler to reach the ceiling. The final\nremainder can be short. A shorter run otherwise needs a specific model limit or the user's explicit\nsplit. For example, six proposed runs of 7, 7, 4, 3, 6 and 3 seconds become one 30-second generation\nwhen the selected model accepts 30 seconds and their combined references fit. The nine shot\ncards and their internal cuts stay separate inside that generation.\n\nWrite the internal cut pairs and each necessary run edge using film-shot-generation's seams\nreference: match action, eyelines and screen direction, keep geography, and carry frames only\nfor its named exceptions. Fewer generations must preserve this method, not replace the cuts\nwith one long shot or buy a bridge for every boundary.\n\n- The board approves camera and seconds. It is not a place to rewrite the story: an edit that\n  changes what happens is a story note, so rewrite the paragraph first, then open the board again.\n- On `shotlist_board_feedback`, **replace** your list with it, runs included. Fields the board does\n  not carry (references, prompt versions, trims) stay on the shot by id.\n- A long scene held in one shot comes with film-shot-generation' coverage recommendation on its card. Keep\n  the single shot only if the user chooses it on the board.\n- A card that film-shot-generation flags for a kinetic move on a big face, set on the board or changed\n  later, gets one short ASK (with the host's own choice tool where it offers one, such as request_user_input in Codex's Plan mode, so the user taps an option; a Picsart board the step names asks there instead; only where neither works, the options numbered in one message, the recommended one first; in unattended pace, never ask: write it to the project record's openDecisions with the answer you assumed, as picsart-video-rules says) before the run is compiled: the move as the user set it, or one of\n  film-shot-generation' safer versions. The camera stays the user's.\n- After a long stretch on one video, offer once to reopen the board to recap what comes next.\n  Honour a no without asking again.\n\n## 5. Cast, places and props\n\n**The project folder first**, before anything is generated. `picsart_drive_create_folder` with\n`path: \"Picsart Films/<film-slug>\"` and\n`children: [\"Library\", \"Assets\", \"Shots\", \"Exports\"]`. Keep every uid it returns in the record.\nSay it once, plainly: \"Created Picsart Films/the-garage in your Picsart Drive, with Library,\nAssets, Shots and Exports inside. Everything this film makes is filed there.\" Never say it again,\nand never list the whole Drive: no `list` without a `folderUid`. Pass the right `folderUid` on\nevery `picsart_generate` and `picsart_job_status` call of the film, and the project folder as\n`projectFolderUid` on every asset call. A finished job is filed only when you save it, as\npicsart-video-rules's SPEND rule 4 says: save every finished picture and take into its folder before you\nshow it. Never call a filed file permanent.\n\nThen film-cast-design's conveyor, in one pass:\n\n1. Draft every descriptor as film-cast-design says, then offer the cast board once\n   (film-cast-design, *The starting point*). It is the one stop here and costs nothing; a reply that\n   ignores it keeps the story's descriptors. There is no other approval round.\n2. Compile each picture with `picsart_film_compile_prompt` (a reference `kind`) and read its\n   `check`, then **one SPEND for the whole batch**: every sheet and plate on one\n   quote.\n3. Dispatch on the yes as one batch (picsart-video-rules, SPEND), with `folderUid` set to Assets, and\n   let the batch's card follow the jobs as picsart-video-rules says.\n4. Look at each picture (picsart-video-rules, Asset URLs) before anything uses it, then put them all on\n   `picsart_film_review_assets` in one call (at most 12 tiles; more go on a second board), with the one thing to judge them by as the board's `judge`, and one line per tile as its `assets[].why`.\n5. Act on the reply as `references/board-replies.md` says. Each approved asset is cut into views and\n   locked with `picsart_film_save_asset`, as film-cast-design says. Before regenerating a rejected\n   picture, save that version as `rejected` and record it as below. The replacement is regenerated\n   under its own SPEND and shown alone on a fresh board, with `assets[].version`; omit `assets[].previousUrl` when the previous picture\n   was rejected. A discarded tile is recorded as rejected and never used.\n\nA person the user photographed is saved as it came and is not put up for approval: it is theirs.\nfilm-cast-design flags what it cannot settle on its own, about a photo the user brought or about the\nfilm's era. Raise each flag once, as one short ASK (with the host's own choice tool where it offers one, such as request_user_input in Codex's Plan mode, so the user taps an option; a Picsart board the step names asks there instead; only where neither works, the options numbered in one message, the recommended one first; in unattended pace, never ask: write it to the project record's openDecisions with the answer you assumed, as picsart-video-rules says) with the options film-cast-design names. Anything\ngenerated is its own SPEND.\n\n### A rejected cast picture\n\nTreat \"Change one\", \"not her\", \"profile is not ok\", \"it's not her\", or any no to a cast picture\nas a rejection. If several pictures were shown and the target is unclear, ASK (with the host's own choice tool where it offers one, such as request_user_input in Codex's Plan mode, so the user taps an option; a Picsart board the step names asks there instead; only where neither works, the options numbered in one message, the recommended one first; in unattended pace, never ask: write it to the project record's openDecisions with the answer you assumed, as picsart-video-rules says) which one\nwithout showing them again; do not regenerate until it is identified.\n\nBefore regenerating, call `picsart_film_save_asset` for the rejected version with `status: \"rejected\"`,\nits original `tag`, `sheetVersion`, `portraitUrl`, `projectFolderUid` and saved asset metadata.\nPass the saved `identityReferences` too. Every new save supplies the user's original photo URLs\nthere, or `identityReferences: []` when all views are generated. Do not infer provenance from a\nview's position; preserve unknown provenance on older records.\nRecord its tag, version, file uid, URL and all extracted view/panel URLs in the project's\n`rejectedAssets[]`, and mark that version's asset row `rejected`. Confirm the save succeeded before\na replacement is generated; on failure keep the local rejected entry and retry the save, never reuse it.\nA replacement gets a new version and stays in review until the user approves it.\n\nNever show a rejected picture again, including in a comparison, `previousUrl`, an old plan card or\nan asset recap. Never pass any part of it as a reference: no full-body front, profile, crop, view\nor panel. Rejecting one view rejects the whole sheet unless the user explicitly said otherwise;\nrecord any such exception and keep only the explicitly permitted view separate from the rejected sheet.\nCheck `rejectedAssets[]` before every display, reference selection, plan and resumed film turn.\nRemove rejected references from pending opening frames and shot plans before continuing.\n\nFor a person made from the user's own photos, keep those original photos in `identityReferences[]`\nand use them as the identity reference for every replacement. Rejecting a generated sheet never\nrejects the user's original photos; do not substitute a rejected generated face for them.\n\n### Location references before shooting\n\nKeep the location map. Follow film-shot-generation's scene-pictures reference: a wide for every\nscene, its opening scene picture cut from that wide, and a room map where the scene cuts between\nwalls. Reuse one map per place and time of day; a single outdoor background uses its wide as its\ngeography. Record the URLs in `scenes[].pictures` and the geography line in `scenes[].geography`.\n\nCompile and verify the required pictures, quote them together with SPEND (quote it in one line, then get the yes as an ASK with \"Yes, go ahead\" / \"Yes, up to N credits for this task\" / \"No\": the host's own choice tool where it offers one, otherwise those options numbered in one message; the host's own confirmation before a tool runs is not this yes; unless a spend limit the user stated covers it: N credits or an explicit no-limit (\"as much as needed\"), never inferred from words like \"go ahead\". Within it, ask nothing: quote it in one line (\"About 8 credits; 12 of 20 left after this\"), call it, then say what it spent and what remains, keeping a running total that includes failed calls, and stop to ask before the first call that would cross it. A money amount is asked once to restate it in credits; in unattended pace, never ask: call only with a consent or a stated spend limit already recorded, otherwise write the quote to pendingSpends and stop, as picsart-video-rules says), then generate the\nindependent pictures in a batch. Check each before its board review, including the cast's faces,\nopening positions and room geometry. Use `picsart_film_review_assets` for the location references\nand apply `references/board-replies.md`. Reuse approved pictures already in the record. A real app's\nscreen is built as a scene layer from the user's screenshots or recording, never generated.\n\n**No still test.** The scene pictures are where the cast is checked, as film-cast-design says.\nA cast or prop correction goes through that asset's conveyor only, under its own SPEND.\n\n**The gate into shooting:** the story and shot list approved, every scene in a run has approved\nlocation references, and film-cast-design's gate into a run holds for all its tags, read back from\n`picsart_film_list_assets`. The opening scene picture starts the scene's first run; later runs use\nfilm-shot-generation's continuity references. No storyboard panels, voiced slideshow or animatic\napproval is required in the default flow.\n\n### Only when the user requests a storyboard or animatic\n\nRecord the explicit request in `requestedPreview` (`kind: \"storyboard\"` or `\"animatic\"`,\n`status: \"requested\"`) and load film-animatic for that work. A request for a **storyboard** uses\nits panel method only: quote and make the requested panels, check them, and review them on\n`picsart_film_review_assets`. It does not buy voices, music or a timed animatic. A request for an\n**animatic** uses its timed-preview method and voice-over-generation for its sound; quote the\nneeded pictures and sound with SPEND (quote it in one line, then get the yes as an ASK with \"Yes, go ahead\" / \"Yes, up to N credits for this task\" / \"No\": the host's own choice tool where it offers one, otherwise those options numbered in one message; the host's own confirmation before a tool runs is not this yes; unless a spend limit the user stated covers it: N credits or an explicit no-limit (\"as much as needed\"), never inferred from words like \"go ahead\". Within it, ask nothing: quote it in one line (\"About 8 credits; 12 of 20 left after this\"), call it, then say what it spent and what remains, keeping a running total that includes failed calls, and stop to ask before the first call that would cross it. A money amount is asked once to restate it in credits; in unattended pace, never ask: call only with a consent or a stated spend limit already recorded, otherwise write the quote to pendingSpends and stop, as picsart-video-rules says), then validate, check and REVIEW the preview as that\nskill says. Reuse the approved cast and location references in either case.\n\nThe request chooses the work, not permission for an unquoted spend. Apply SPEND (quote it in one line, then get the yes as an ASK with \"Yes, go ahead\" / \"Yes, up to N credits for this task\" / \"No\": the host's own choice tool where it offers one, otherwise those options numbered in one message; the host's own confirmation before a tool runs is not this yes; unless a spend limit the user stated covers it: N credits or an explicit no-limit (\"as much as needed\"), never inferred from words like \"go ahead\". Within it, ask nothing: quote it in one line (\"About 8 credits; 12 of 20 left after this\"), call it, then say what it spent and what remains, keeping a running total that includes failed calls, and stop to ask before the first call that would cross it. A money amount is asked once to restate it in credits; in unattended pace, never ask: call only with a consent or a stated spend limit already recorded, otherwise write the quote to pendingSpends and stop, as picsart-video-rules says) to every new\ncharged operation. On approval, set `requestedPreview.status: \"approved\"` and continue to\nshooting; no second shot-selection question is added. Storyboards and animatics are never\nrequired, recommended as another gate, or created on a resume without that explicit request.\n\n## 6. Shooting\n\nShoot the approved shot list directly, respecting any explicit exclusions the user already made.\nDo not ask them to choose the shots again. Use the approved scene-opening images and continuity\nreferences as film-shot-generation says; never require one generated panel per shot.\n\n**Recheck capacity before the forecast or quote**, including on resume. Reconcile the approved\nshot cards, current model limits and planned runs; show the generation count and each run's\nseconds against the ceiling. A batch with six items is still six generations. Do not quote\nmergeable short runs. If correcting them changes approved run boundaries, show that correction\nin the existing approval/quote step; keep the user's explicit splits, shot choices and seconds.\nRecompile the corrected runs and their joins, and replace the old quote. Never repack a submitted\nor completed job into another paid generation; keep its handle and existing footage.\n\nBefore any run is quoted, a shot that film-shot-generation flags for a palette arguing with the film's\nscheme gets one short ASK (with the host's own choice tool where it offers one, such as request_user_input in Codex's Plan mode, so the user taps an option; a Picsart board the step names asks there instead; only where neither works, the options numbered in one message, the recommended one first; in unattended pace, never ask: write it to the project record's openDecisions with the answer you assumed, as picsart-video-rules says) with its options.\n\n1. **The forecast, once, before the first video:** runs × each run's seconds at the model's draft\n   rate from `picsart_preflight`, plus a margin for repairs, and the finish beside it. It is an\n   estimate, not a quote.\n2. **Shoot every run as a draft, in one batch**, as film-shot-generation says: the model's draft\n   setting or its lowest resolution, and no test run first. Every independent run is compiled,\n   verified and sent together, one call per run: one quote for the batch with the finish priced\n   beside it as an estimate, one yes, one monitor. The yes buys the drafts only. A run that waits for an earlier take (its frames\n   are the references) is its own SPEND once that take lands and passes your check.\n3. **No film so far.** While takes run, never assemble, cut, open or show the film so far: a landed\n   take waits for the others. As each take lands, find its actual cuts and judge it as\n   film-shot-generation's takes reference says. That is your technical check, not acceptance:\n   every take stays a candidate until the user approves the cut (7). No question between the\n   takes and the cut.\n4. Dialogue is judged in the cut's REVIEW, by ear. Say that the words were not checked against the\n   script by a tool.\n\nShooting is done when every take has landed and passed your check, with its actual cuts, prompt,\nquote and handle in the record. No take is accepted yet.\n\n## 7. The cut\n\nWhen the last take lands, film-cutting assembles the film once: every candidate take in story order\nwith hard cuts, every generation one clip exactly as generated: no split at a run's internal cuts,\nno trims, no transitions, padding or freeze frames. The user's own trims and splits are kept and\nnever recomputed. Check it with quality-review, its cold watch included (quoted first with its own SPEND (quote it in one line, then get the yes as an ASK with \"Yes, go ahead\" / \"Yes, up to N credits for this task\" / \"No\": the host's own choice tool where it offers one, otherwise those options numbered in one message; the host's own confirmation before a tool runs is not this yes; unless a spend limit the user stated covers it: N credits or an explicit no-limit (\"as much as needed\"), never inferred from words like \"go ahead\". Within it, ask nothing: quote it in one line (\"About 8 credits; 12 of 20 left after this\"), call it, then say what it spent and what remains, keeping a running total that includes failed calls, and stop to ask before the first call that would cross it. A money amount is asked once to restate it in credits; in unattended pace, never ask: call only with a consent or a stated spend limit already recorded, otherwise write the quote to pendingSpends and stop, as picsart-video-rules says) unless\nevery call is quoted at 0 credits; on a no, the review line says \"no cold watch yet\"), then REVIEW the whole cut, unasked and opened cold: this is the film's review. Once the user has\nanswered, say what your check observed in each take. **The user's approval of the cut\naccepts every take in it**, and its shots become `final`.\n\n**Notes route by meaning**, as film-shot-generation says: an edit, an extend or a re-roll. A note it\nflags as ambiguous gets one short ASK (with the host's own choice tool where it offers one, such as request_user_input in Codex's Plan mode, so the user taps an option; a Picsart board the step names asks there instead; only where neither works, the options numbered in one message, the recommended one first; in unattended pace, never ask: write it to the project record's openDecisions with the answer you assumed, as picsart-video-rules says) between its two routes. **Each is its own SPEND**, shot as a draft\nlike the takes: a yes to a run is not a yes to its repair. A note on a seam is not a licence to buy footage: film-cutting's\njoin repair diagnoses first. A bridge between two runs is its own SPEND too, reviewed as\nfilm-cutting's join repair says. Apply what the user points at, re-cut once and open it again, until\nthey call it final. After that, change no picture unless they ask.\n\n## 8. Finishing\n\nIn this order, as film-finishing says: the finish of the draft takes, then colour, then sound.\n\n1. **Finish the approved cut**, as film-finishing says: from each draft's `finalizeDraft` handle\n   where it has one, otherwise an upscale or the approved run generated again at the finish\n   settings. It is its own SPEND (quote it in one line, then get the yes as an ASK with \"Yes, go ahead\" / \"Yes, up to N credits for this task\" / \"No\": the host's own choice tool where it offers one, otherwise those options numbered in one message; the host's own confirmation before a tool runs is not this yes; unless a spend limit the user stated covers it: N credits or an explicit no-limit (\"as much as needed\"), never inferred from words like \"go ahead\". Within it, ask nothing: quote it in one line (\"About 8 credits; 12 of 20 left after this\"), call it, then say what it spent and what remains, keeping a running total that includes failed calls, and stop to ask before the first call that would cross it. A money amount is asked once to restate it in credits; in unattended pace, never ask: call only with a consent or a stated spend limit already recorded, otherwise write the quote to pendingSpends and stop, as picsart-video-rules says), after the cut is approved, asked as film-finishing's one\n   question: finish the approved takes, or keep the drafts. Then the cut is re-assembled at the\n   finish size with the user's trims.\n2. **Colour:** ASK (with the host's own choice tool where it offers one, such as request_user_input in Codex's Plan mode, so the user taps an option; a Picsart board the step names asks there instead; only where neither works, the options numbered in one message, the recommended one first; in unattended pace, never ask: write it to the project record's openDecisions with the answer you assumed, as picsart-video-rules says) with three or four looks that suit the film, from the look list in\n   `picsart_scene_capabilities` (`sections: [\"looksCompact\"]`). Applying one is free.\n   When the takes look glossy or plastic, as generated footage often does, one option is the\n   realism grade, applied as the realistic-color-grade skill says.\n3. **Music:** offer it once, only after the cut is final, and never bare: ASK (with the host's own choice tool where it offers one, such as request_user_input in Codex's Plan mode, so the user taps an option; a Picsart board the step names asks there instead; only where neither works, the options numbered in one message, the recommended one first; in unattended pace, never ask: write it to the project record's openDecisions with the answer you assumed, as picsart-video-rules says) with the brief\n   drafted as the background-music skill says, and three exits: generate it, change the brief, or skip. A\n   changed brief is redrafted and asked again; a skip is settled for the session. A yes is a SPEND,\n   as picsart-video-rules says. Lay the bed as film-finishing says, then REVIEW the film with it, on how it\n   sits under the dialogue. A note on its level moves it as the background-music skill says; a different\n   track goes back through the background-music skill's brief, with a new SPEND. A film going to festivals\n   or dubbing gets film-finishing's sound-team handoff offered once.\n\n## 9. Deliver\n\nDELIVER the final cut once, as picsart-video-rules says. Any further master from film-finishing's delivery\nlist is confirmed with one ASK before the first is exported. A master in another shape is reframed as the\nfootage-reframing skill says.\nThen film-finishing's archive and disclosure: give the user the disclosure text (every model used,\nper stage) and record it, and say generated music's licence is theirs to check before a festival or\na commercial use.\n\n## When something fails\n\n- **Out of credits: zero retries.** Say which step is paused and what it needs against the balance\n  `picsart_credits` reads. Keep the record and every job handle. Continue only when the user says\n  their credits are there; never poll the balance.\n- **A dropped call is not a failed generation**: follow its job as film-shot-generation says.\n- **A board that errors on a value** gets the value fixed and the board sent again. A board the\n  host cannot draw gets the host notes' fallback, and the gate still holds.\n- **Anything else a stage cannot run without** gets one identical retry, then one plain line: what\n  you tried, what blocked it, what you need. Never reword and refire.\n- **An outage is status, not a decision.** Keep going on everything free, keep the blocked item in\n  `openDecisions`, and try again next turn. Never offer a choice the rules already answer, such as\n  giving up a lead's consistency to dodge a temporary outage.\n"
}

SHA-256 of public snapshot: b25cd21c3d6a6a714cb8f7f7cc576adb191634a35467e57d67c3274ffacfcad0