Templates and Workflows

Single prompt generation is useful for exploration. Templates are how that exploration becomes a repeatable workflow.

Why templates matter

Many teams do not want to rewrite a prompt from scratch every time.

They want a structure like:

• the same campaign format every week
• the same product story with new variables
• the same multi-scene outline across many variations

That is what the template layer is designed to support.

Current workflow model

The product already includes foundations for template-driven projects:

• template variables
• ordered scenes
• project-level planning
• project scenes submitted into real video generation
• status tracking across the project lifecycle

At the system level, projects move through states such as:

• draft
• planning
• generating
• composing
• completed
• failed

How a template project works

In practical terms, the flow looks like this:

1. Choose a template.
2. Fill in variables such as product name, audience, or campaign angle.
3. Generate scene prompts from the template structure.
4. Submit queued scenes into video generation.
5. Track scene and project status until outputs are ready.

Best use cases

Templates are most useful when you produce video in recurring formats:

• product promos
• ad variations
• creator series formats
• launch sequences
• internal content pipelines

What is available now vs later

Available now:

• the product direction and data model for template projects
• scene-based orchestration foundations
• project tracking tied to real generation tasks

Being built next:

• smoother end-to-end agent flows
• better composition between scenes
• stronger reusable template operations for repeat production

Recommended way to use templates

• First find prompts that already work in manual generation.
• Turn those winning patterns into variables and scenes.
• Use templates for consistency, not for hiding weak creative direction.

Templates work best after you already know what a good result looks like.