Responsibilities and Goals
Complete project operations and agreed deliverables under confirmed creative decisions, restore the existing project and preservation items, and check affected content and actual outputs. Detailed methods are provided by the shared specification; this entry point handles access for general engineering tasks.
The Agent selects an entry point based on the intent of the current round; specialized tasks can go directly to the corresponding Skill. Whether a project originates from a template or a recreation does not determine the entry point for each subsequent round; the same Agent reuses the project and decisions to continue execution.
1. Restore the scope of this round
Read shared context, reuse the existing brief, assets, project, authorization, and still-usable read text. Restore the current stage, preservation items, and completed operations, and fill in dependencies according to this round's task. Continuation status comes from the session, existing records, and the actual project; having only read the entry point does not mean the status has been restored.
This entry point applies to modifying text, colors, or local timing according to established requirements in an existing editable project, replacing selected assets/music, adjusting volume, opening previews, technical checks, project troubleshooting, and export-only tasks. When there is only a finished video file or link and no corresponding editable project, enter openmotion-recreate; an MP4 cannot be directly treated as an editable project. When new narrative, motion, or audiovisual arrangement is needed, enter the corresponding scope according to the specialized navigation below; local creation only expands the affected content.
2. Project Operations and Delivery
- When modifying existing content, read shared modification process, determine changes, preservation items, and associated impacts; for query-only, preview, review, or export, execute according to the scope of this round.
- Existing-project content edits apply the continuing-edit preview rules before writing and after saving, including scoped engineering work. Preserve the current chat by default; queue its latest preview while inactive and inspect it on return. Only an explicit show-now request permits switching back for this turn. Before operating on the project, read operational specification; before writing native content, also read Native authoring and the fixed-version engine guide returned by the tool. Confirm projectId, latest revision, and currentVersionId, and reuse completed operations.
- Fill in the affected quality specifications according to the dependency list in the shared context. Replacing existing music or adjusting volume also requires checking audiovisual anchors and existing SFX; when the visuals are locked, preserve the visual content. Return the supplementary reading results to the model first, and execute dependent operations in subsequent calls.
- Check the affected intervals, junctions, and preservation items. For exports or finished-video delivery that require new rendering, read verification, export for the reviewed revision/versionId, and for existing applicable tasks, query and reuse first; for template-based video production, verify in the editor according to the specialized entry point, and when export is needed, check the actual MP4. Technical pass and creative quality, normal playback, and audition are recorded separately.
- Stop at the plan, preview, project, or finished-video stage requested by the user. Deliver the actual results, checks, and necessary limitations. The project opened in the editor is the deliverable; attach an MP4 only when the user explicitly asks for an MP4, video file, download, or export.
Specialized Navigation and Legacy Call Compatibility
The following navigation is for cases where an entry point has not yet been selected or legacy production/start Use for invocation; clear professional tasks go directly to the corresponding entry. General engineering tasks do not need to restart the professional creative workflow just to complete quality specifications.
| This round's task | In scope |
|---|---|
| Original new films, motion graphics, creative proposals, large-scale narrative re-editing | openmotion-director |
| Redesign local motion, pacing, sound narrative, or evaluate creative quality | Local creation/review scope of openmotion-director; even if the picture is locked, sound can be designed alone |
| Use an already selected editable template or source code to adapt content | openmotion-template-to-video, preserving as-is delivery and content adaptation implementation |
| Explicitly request rebuilding a reference video into a reusable template folder or ZIP | openmotion-video-to-template |
| Rebuild this work based on the actual video; when there is only a finished file/link and no corresponding editable project, even if only a few words are changed | openmotion-recreate, follow the existing replication method and digital measurement |
| The reference video only provides stylistic inspiration | openmotion-director |
| Accept the first-experience invitation after installation | openmotion-template-to-video; follow the exact template ID, native duration, standalone project, and editable preview that the user accepted in this invitation; for the three candidates' "yes", clarify first |
Ambiguous requirements are judged in combination with user goals and existing materials; only fill key gaps that affect routing or authenticity. Links and files are input forms and do not automatically equal replication. Template sources and exact IDs are checked against template capability description ; when an original new film needs its brief completed, use requirements and records。
Local and MCP share the same source
Relative links are resolved based on this file's location. MCP-only discovers via resources/list and reads the same-source body via resources/read: this entry is openmotion://workflow/production/start; shared pages use production's context, edit, production, native, verification, templates, intake, portable; professional entry short IDs are director, template, recreate, video-to-template, each reading start. The fixed engine guide is openmotion://engine/SKILL.md。
Existing workflow short IDs and shared document paths remain compatible; the old default production/start can still navigate to professional entries; phase one does not provide an independent workflow-reading Tool. The returned references provide exact addresses; use documentId/contentHash to identify versions, and reuse only complete bodies that have actually been read and are still in context. Reading guidance does not start services, modify projects, or prove actual execution compliance.