| name | agentic-video-architecture |
| description | Use when designing Clash video production workflows, skill packs, local/agent-first project structure, pipeline manifests, stage gates, file projections, CAS apply, or black-box QA for video/image generation workflows. |
Agentic Video Architecture
Use this skill before implementing or planning a new Clash production workflow.
It turns a video request into a staged pipeline that agents can operate through
files while product state remains protected by explicit apply commands.
Core Pattern
Treat every workflow as a project-local pipeline:
brief/ human and agent editable
references/ source media and rights notes
assets/ immutable generated/imported media
analysis/ machine-readable media intelligence
plans/ agent-editable decisions
projections/ CAS-protected canvas/timeline files
exports/ rendered outputs and validation reports
pipeline.manifest.json stage graph, gates, dependencies
The canvas is a view. snapshot.bin and DB files are not editing surfaces.
Agents can write drafts and plans, then apply product state through Clash CLI or
host APIs.
Stage Model
Use these stages unless a workflow has a strong reason to differ:
brief: product goal, audience, format, duration, constraints.reference-ingest: public references, brand media, raw footage, source URLs.analysis: audio, transcript, shot, image, rights, or visual moment metadata.plan: storyboard, cut plan, prompt pack, style plan, delivery specs.generate: image/video/audio/MG assets, always versioned.assemble: timeline projection, captions, overlays, asset references.review: QA gates, legal/brand checks, stale-write checks.export: rendered files plus validation report.
Each stage writes a clear artifact. Avoid invisible agent memory.
Safety Rules
- Do not ask agents to edit
snapshot.bin, SQLite, Loro files, credentials, or
runtime directories.
- Any
pull -> edit -> apply flow needs CAS.
- Referenced media is immutable; changing it creates a new asset or version.
- Public reference video ingestion needs a rights/source ledger.
- Expensive generation and final export should pass stage gates.
- In Clash-managed local runs, represent those gates with
an explicit review-gate artifact plus an explicit approval step; the approval must use the
path-bound CAS lock generated for the same gate file. Agents should not
silently treat missing QA artifacts as approved.
- Black-box E2E should verify artifacts from outside the implementation path.
Output Contract
When using this skill, produce:
{
"pipeline": "short-drama | mv | talking-head | tvc | image-pack | custom",
"stages": ["brief", "analysis", "plan", "generate", "assemble", "review", "export"],
"editableFiles": [],
"protectedFiles": [],
"requiredSystemCapabilities": [],
"missingSystemCapabilities": [],
"qaChecks": []
}
Migration Notes
- OpenMontage suggests pipeline manifests, stage directors, and broad tool maps.
- HyperFrames suggests agent-friendly editable React composition authoring plus
domain skills; Clash delivers that source through its Remotion Canvas node and
Timeline path.
- Montage-style systems suggest keeping deterministic analysis independent of
optional LLM creative direction.
