Vizard Agent

How to get a reusable recipe so you can repeat the job yourself

Last updated 2026-09-15 · 8 min read

When a job finally comes out right, ask Vizard Agent to write the brief that would have got there first time. Everything you corrected along the way is a requirement you never stated, so it collects those — the levels, the framing rules, the things you had to say twice — into something you can paste at the start of the next one.

What is the short version?

A long job teaches both of you what the job actually was. All of that knowledge sits in the conversation you just had, and the next batch of footage starts from a blank page unless somebody writes it down somewhere.

  1. Finish the job with Vizard Agent as normal.
  2. Ask it for a reusable brief based on what you corrected.
  3. Keep that brief with the project, not in the chat.

What do you need before you start?

A finished job you are actually happy with. Vizard Agent derives the recipe from what happened along the way, so asking for it before the result is right simply produces a careful brief for a video you did not want in the first place.

What do you type into Vizard Agent?

Ask Vizard Agent for a brief rather than a summary. A summary describes what happened during the job; a brief is written as instructions meant to be followed, and only one of those two is any use pasted into a new conversation.

Prompt

This is right now. Write me a reusable brief I can paste at the start of the next batch of rushes to get to this result faster — include the levels and settings we landed on, anything I had to ask for twice, and the checks that caught problems.

Variants worth knowing:

What does Vizard Agent actually do?

Here is what it produces at the end of a job that took many rounds. Note that it is written last — the brief is a product of the corrections, so it cannot be written before they happen.

  1. Reads back over the whole job.
  2. Collects the settings that were argued over.
  3. Notes what you asked for more than once.
  4. Records the levels and measurements that were settled.
  5. Includes the checks that found the problems.
  6. States what must not be changed next time.
  7. Leaves a slot for what will differ — the new footage.
  8. Writes it as instructions rather than as a report.

Step three is the most valuable line in the brief. Anything you had to repeat was a requirement that was not obvious, and those are exactly the things that will be got wrong again unless they are written down.

Step five is the half people leave out. A brief that lists settings gets you the same look; a brief that also says "check the music is audible on a phone" gets you the same standard, which is what actually took the rounds.

Step seven is what makes it reusable rather than a record. A brief with the last job's specifics baked in produces the last job again, so the parts that will change are marked as parts that will change.

What does the result look like?

A short document you paste in at the start of the next job. The next one arrives much closer to right on its first attempt, and the rounds you do end up spending are about the new footage rather than about relearning preferences you already explained once.

Vizard Agent will also revise it after the next job, so the brief accumulates what it learns rather than going stale sitting in a folder.

When does this not work well?

A recipe encodes one particular kind of job, and Vizard Agent will say when yours has moved. Different footage, a different format or a different purpose will not fit it, and following a brief that no longer applies is worse than starting from nothing.

How do you fix a result that came back wrong?

Tell Vizard Agent what the brief missed. Because it is a document rather than something held in a conversation, adding the missing rule is an edit you make once and it then applies to every job you run afterwards.

How does Vizard Agent compare to doing it yourself?

By hand the lessons stay in a chat log nobody reopens. The next job starts from the same blank brief, the same corrections get made in the same order, and the only thing that improves is your patience.

By hand Vizard Agent
Where the lessons live The conversation A brief you keep
What gets captured The final settings Settings, repeats and checks
Next job Starts from nothing Starts from the recipe
Improvement None between jobs The brief accumulates
When it is written Never At the end, from what happened

Common questions

When should I ask for it? At the end, once the result is right. Vizard Agent writes it from the corrections.

Why not write it myself? You can, though Vizard Agent catches the things you corrected without noticing you had.

Will it include my measurements? Yes. Vizard Agent records the levels and settings that were actually settled on.

Can it be a file? Yes, and Vizard Agent would rather deliver it as one than as a message.

Does it work across projects? Yes, for the same kind of job. Different formats need their own.

Can it update the brief later? Yes. Ask Vizard Agent to revise it after the next job.

What if my taste changes? Then the brief changes with it; it is a document, not a rule.

Should it include the checks? Yes. Vizard Agent includes them, because those are what took the rounds.

Can I share it with a colleague? Yes, and Vizard Agent will work to it for them too, which is usually the point.

Will it make the next job instant? No, but Vizard Agent should start it much closer to right.

What if the footage is different? Vizard Agent leaves a slot for that rather than baking it in.

Can it write one for a series? Yes, and that is where it pays off most.

Does it replace the conversation? No. It replaces having the same conversation twice.

Why is it written at the end? Because the corrections are the specification, and none of them exist before the job is done.