production-campaign
Coordinates writing, review and media execution across commissioned productions by launching each writer and reviewer as its own CLI process, keeping an observer subagent on them and connecting independent review. Use for sustained authoring campaigns, explicit single-production observation and production comparisons.
- License 许可
- MIT
- 最近更新
- 2026-11-15
- Stars
- ★ 15
- Forks
- 3
01 前言 Front Matter
- name
- production-campaign
- description
- Coordinates writing, review and media execution across commissioned productions by launching each writer and reviewer as its own CLI process, keeping an observer subagent on them and connecting independent review. Use for sustained authoring campaigns, explicit single-production observation and production comparisons.
02 资源文件 6
- 参考文档comparing-productions.md643 B
- 参考文档connecting-review.md3.1 KB
- 参考文档git-ownership.md1.2 KB
- 参考文档launching-workers.md3.0 KB
- 参考文档observing-runs.md3.2 KB
- 参考文档run-records.md1.8 KB
03 SKILL.md 正文
Production campaign
A campaign carries commissioned work through its actual authoring and delivery owners. Its coordinator, working from this repository, launches, watches and connects the workers and compares productions.
| Task | Read |
|---|---|
| Preparing a production, launching writers and reviewers, their write scope | Launching workers |
| Writing the run record, resuming a run, handing off | Run records |
| The observer subagent's ticks and the revival of a stopped run | Observing runs |
| Fixing a submission, launching an independent reviewer, relaying verdicts and rebuttals | Connecting review |
| Staging and committing beside other workers | Git ownership |
| Comparing productions | Comparing productions |
Give Observing runs to the observer as its brief.
Owners
The production's sustained runs guide owns its run record, dispatch, film and module ownership and resumption, and its specialist skills own creation and acceptance. Repository issue campaigns own broad engineering audits and issue publication.
These rules stay here rather than in the scaffold, because the scaffold ships to everyone who installs AutoMovie and their productions are not bound to this repository's process launching or observation. The production's guide leaves observation to an available scheduler and additional agents to the user's authorization; this repository chooses an observer subagent as that scheduler and CLI processes as those agents.
Authority
A campaign the user starts authorizes its writers, reviewers and observer within the requested productions and scope. A request only to observe authorizes resuming existing runs, not starting new writers. Keep that scope and the current baseline explicit.
A single film's observed execution establishes that film's behavior, not comparative quality across productions, and instruction edits alone establish no improvement in a screenplay or film.
Missing capabilities and viewers
A missing capability that a real authoring or playback task exposes is work to complete, not a reason to lower the commission or hide a local substitute. Trace it through project ownership, implement and validate it through development, then reconnect its actual production consumer.
Scaffold changes reach only new productions; source, configuration, instruction and contract migrations of an existing production remain deliberate project changes.
Apply the production's viewer recovery priority before continuing dependent creative or visual judgments. A working preview does not certify capture, encoded-video playback or final delivery. Follow the exact failing path through repair and report observed and unperformed checks separately.
04 同仓库更多 Skills
story-workflow
Chooses the story route and who writes the screenplay, and routes to each route's steps and to completion. Use when starting, resuming or completing narrative work.
story-correction
Inspects a narrative body and repairs it by cause, at its earliest owner and within closed boundaries. Use before evidence, after review findings, or when requirements or scope change.
development
Implements and tests production source, integrations, dependencies and commands, reusing installed packages before writing a capability. Use for code or host changes and behavioral tests; documentation owns technical writing and story owns creative bodies.
pull-request
Branches, commits, pushes, opens, updates, and merges automovie pull requests. Use only when the user asks for one of those actions or a mandate names delivery.
issue-campaign
Runs automovie's issue campaign, repeating full discovery rounds until one finds nothing new, publishing the issues, and landing them in one pull request per cycle. Use for a broad audit or repeated issue-to-pull-request work, not for one defined issue.
documentation
Owns how any document is written, with its sentences, terms, paragraphs and lists, and what a README holds. Use before writing or changing a technical document, README or doc comment; instructions for an agent add the prompting skill's rules.