Video Consultant Workflows
The archon-video-* workflow family turns Archon into a video design and production consulting system.
It supports:
- solo founder launches
- consultant/client launches
- creator or brand launches
The default completion standard is published + measured. The system does not stop at “creative approved” or “assets ready”.
Workflow Map
Section titled “Workflow Map”| Workflow | Use When | Output |
|---|---|---|
archon-video-consultant-lifecycle | You need the full ODD lifecycle | Outcome package, creative + production + launch + post-launch artifacts |
archon-video-intake-to-brief | You need discovery and launch framing | Outcome specification, launch brief, offer-message fit |
archon-video-script-and-storyboard | You need creative development | Creative brief, script, storyboard |
archon-video-production-pack | You need execution planning | Shot list, production plan, edit brief |
archon-video-edit-and-versioning-plan | You need cutdown and channel planning | Edit brief, versioning matrix |
archon-video-launch-readiness | You need the publishing package | Launch runbook, go-live checklist, publish package |
archon-video-go-live-ops | You need independent launch QA | Lane evidence, evidence package, convergence report |
archon-video-post-launch-review | You need the first review cycle | Post-launch review, optimization plan |
archon-video-content-ops-cycle | You need recurring follow-on operations | Optimization plan and next content cycle |
Flagship Workflow
Section titled “Flagship Workflow”Use the full lifecycle when the consultant needs to own the system end to end:
archon workflow run archon-video-consultant-lifecycle "Launch a creator-led course with a hero landing-page video, demo cutdowns, testimonial clips, and a post-launch review package"The lifecycle does this:
- Defines the outcome and launch brief
- Builds strategy and creative
- Produces script, storyboard, and production artifacts
- Produces the go-live package
- Runs Lane A and Lane B independently
- Merges evidence and scores convergence
- Produces post-launch analysis and optimization
Human approvals are required at:
- outcome approval
- creative approval
- go-live approval
- convergence signoff
- post-launch review handoff
Artifact Model
Section titled “Artifact Model”These workflows write a shared artifact set so narrower workflows can pick up where broader ones stop:
outcome-specification.mdlaunch-brief.mdoffer-message-fit.mdcreative-brief.mdscript.mdstoryboard.mdshot-list.mdproduction-plan.mdedit-brief.mdversioning-matrix.mdlaunch-runbook.mdgo-live-checklist.mdpublish-package.mdlane-a-evidence.mdlane-b-evidence.mdevidence-package.mdconvergence-report.mdpost-launch-review.mdoptimization-plan.md
Skills
Section titled “Skills”The video workflows use phase-specific skills instead of one large generic skill:
video-consultant-intakevideo-go-to-market-strategyvideo-creative-developmentvideo-production-opsvideo-launch-opsvideo-post-launch-analysisvideo-quality-review
This keeps each node focused on the job it is doing.
Related
Section titled “Related”- Remotion Video Generation for direct asset generation
- Per-Node Skills for how consultant skills are loaded into nodes
- Approval Nodes for human signoff gates