Kanban Video Orchestrator — Plan and run multi-agent video production pipelines
Kanban Video Orchestrator — Plan and run multi-agent video production pipelines
Start with meaning, then move to detail.
This lesson explains Kanban Video Orchestrator — Plan and run multi-agent video production pipelines as part of getting started with Hermes correctly. You will learn what it does, when it matters, and the smallest safe test that proves it works.
If you are new, do not memorize names. Focus on three questions: what problem does this solve, what access does it need, and how can you verify the result?
For practice, inspect the first example, identify its effects, run it on test data, and compare the result with the source claim.
For advanced readers, inspect Skill metadata, Reference: full SKILL.md, When NOT to use this skill, then verify failure modes and version compatibility.
No prior experience is required; follow the steps on a safe test setup first.
A clear outcome before you read.
- Understand Kanban Video Orchestrator — Plan and run multi-agent video production pipelines without assumed prior knowledge.
- Separate the source description from what still needs testing in your environment.
- Read the first command and identify its inputs and outputs before copying it.
Short definitions before the details.
- Skill
- An instruction bundle that teaches Hermes a repeatable workflow without necessarily adding an external service.
Plan and run multi-agent video production pipelines
What does the source say, and in what order?
- 01Skill metadata
Start here to understand the core idea or structure.
- 02Reference: full SKILL.md
Read this after the foundation, then connect it to the previous step.
- 03When NOT to use this skill
Read this after the foundation, then connect it to the previous step.
- 04Workflow
Read this after the foundation, then connect it to the previous step.
- 05Step 1 — Discover (ask the right questions)
Read this after the foundation, then connect it to the previous step.
- 06Step 2 — Brief
Read this after the foundation, then connect it to the previous step.
- 07Step 3 — Team design
Read this after the foundation, then connect it to the previous step.
- 08Step 4 — Setup
Read this after the foundation, then connect it to the previous step.
- 09Step 5 — Execute
Read this after the foundation, then connect it to the previous step.
- 10Step 6 — Monitor and intervene
Finish here to verify the result and special cases.
Copy only after you understand the effect.
DISCOVER → BRIEF → TEAM DESIGN → SETUP → EXECUTE → MONITORhermes kanban watch --tenant <project-tenant> # live events
hermes kanban list --tenant <project-tenant> # board snapshot
hermes dashboard # visual board UISKILL.md ← this file (workflow + rules)
references/
intake.md ← discovery question banks per style
role-archetypes.md ← role library (writer, designer, animator, …)
tool-matrix.md ← skill + toolset mapping per role
kanban-setup.md ← setup script structure & profile config
monitoring.md ← watch + intervene patterns
examples.md ← six worked pipelines
assets/
brief.md.tmpl ← brief skeleton
setup.sh.tmpl Read the first command and identify its inputs and outputs before copying it.
Match every command to your installed Hermes version, review the files and accounts it can reach, and use non-sensitive data for the first test. If this explanation differs from the source, the official source wins.