Creative Ops Copilot
What to do
1) Ask for (or infer) the input brief:
- - Paste text directly, or
- Provide a file path to a brief/email/thread export.
2) Produce these outputs (always):
- -
docs/creative-ops/plan.md (client-ready) - INLINECODE1 (structured line items)
- INLINECODE2 (ready for API import later)
3) If Chris wants it, also:
- - Create a project folder skeleton (AE/C4D/Octane-friendly) with a
docs/README.md. - POST the invoice draft to the local invoicing API (only if base URL is configured and Chris says “push it”).
Canonical output structure (plan.md)
- - Project summary (one paragraph)
- Goals / Success criteria
- Deliverables (matrix)
- Format, duration, aspect ratios, versions, audio deliverables
- what’s included, what’s not, number of review rounds
- - Open questions (what you still need answered)
- Production plan
- phases + milestones + review windows
- - Risks / dependencies
- Estimate
- line items + hours + rate + subtotal + contingency
How to generate reliably
Prefer generating structured data first, then render it:
1) Extract entities
- - Client name
- Project name
- Deadline/date constraints
- Deliverables list
- Constraints (brand, legal, footage supply, approvals)
2) Decide the production approach
- - Template-driven vs bespoke
- 2D AE vs 3D C4D vs mixed
3) Estimate with motion/VFX realism
- - Prepro (briefing, styleframes, boards)
- Production (anim, 3D, comp)
- Audio/music/licensing (if applicable)
- Renders, exports, versioning
- PM/admin buffer
Scripts (recommended)
Use the bundled script to create consistent outputs:
CODEBLOCK0
If the brief is a file:
CODEBLOCK1
To also create a project skeleton:
CODEBLOCK2
To attempt pushing the invoice draft to your local invoicing API (only if configured):
CODEBLOCK3
Configuration
Optional config file:
Copy to:
Then edit:
- - INLINECODE6
- INLINECODE7 (if needed)
- INLINECODE8 defaults
Notes
- - Keep outputs concise, clean, and client-ready.
- When anything is missing/ambiguous, surface it under Open questions instead of guessing.
创意运营助手
操作内容
1) 询问（或推断）输入简报：
- - 直接粘贴文本，或
- 提供简报/邮件/线程导出的文件路径。
2) 生成以下输出（始终执行）：
- - docs/creative-ops/plan.md（客户就绪版）
- docs/creative-ops/estimate.json（结构化明细项）
- docs/creative-ops/invoice-draft.json（后续可直接导入API）
3) 如Chris要求，还需：
- - 创建项目文件夹骨架（兼容AE/C4D/Octane），内含docs/README.md。
- 将发票草稿提交至本地开票API（仅当已配置基础URL且Chris明确指示“推送”时执行）。
标准输出结构（plan.md）
- - 项目摘要（一段落）
- 目标/成功标准
- 交付物（矩阵表）
- 格式、时长、宽高比、版本、音频交付物
- 包含项、排除项、审核轮次数量
- 阶段+里程碑+审核窗口
- 明细项+工时+费率+小计+应急储备
可靠生成方法
优先生成结构化数据，再进行渲染：
1) 提取实体
- - 客户名称
- 项目名称
- 截止日期/时间约束
- 交付物清单
- 约束条件（品牌、法律、素材供应、审批流程）
2) 确定制作方案
- - 模板驱动 vs 定制化
- 2D AE vs 3D C4D vs 混合方案
3) 基于动态/VFX实际经验进行估算
- - 前期准备（简报、风格帧、故事板）
- 制作阶段（动画、3D、合成）
- 音频/音乐/授权（如适用）
- 渲染、导出、版本管理
- 项目管理/行政缓冲
脚本（推荐）
使用配套脚本生成统一输出：
powershell
python skills/creative-ops-copilot/scripts/creativeopscopilot.py --brief <粘贴简报> --out .
如简报为文件：
powershell
python skills/creative-ops-copilot/scripts/creativeopscopilot.py --brief-file C:\路径\to\简报.txt --out .
如需同时创建项目骨架：
powershell
python skills/creative-ops-copilot/scripts/creativeopscopilot.py --brief ... --out . --skeleton
如需尝试将发票草稿推送至本地开票API（仅当已配置时）：
powershell
python skills/creative-ops-copilot/scripts/creativeopscopilot.py --brief ... --out . --push-invoice
配置
可选配置文件：
- - skills/creative-ops-copilot/references/config.example.json
复制至：
- - skills/creative-ops-copilot/references/config.json
然后编辑：
- - invoicingApi.baseUrl
- invoicingApi.apiKey（如需要）
- rateCard 默认值
注意事项
- - 保持输出简洁、清晰、客户就绪。
- 当任何信息缺失或模糊时，将其列入待解决问题而非自行猜测。
