为什么 AI 生图生视频也要写需求简报？

因为团队生产需要复现和交接。只保存结果图或视频，无法解释为什么成功、为什么失败，也无法控制后续成本。

参考图可以随便上传吗？

不可以。参考图要确认来源、授权和可商用边界，涉及人像、商标、商品或未公开素材时尤其要谨慎。

AI 生图生视频需求简报模板：提示词、参考图、比例、时长和审核字段

作者：ALLTKN 编辑团队路更新于 2026-06-30

用于运营、设计和内容团队提交 AI 生图、图生图、文生视频、图生视频任务的需求简报模板，覆盖提示词、参考图授权、比例、分辨率、时长、任务 ID、下载、审核和复用限制，让高成本创意任务可以复盘、交接和持续优化。

什么时候使用这个模板

适用对象：内容运营团队、电商视觉团队、短视频团队、需要批量生成素材的业务负责人。这类模板适合把重复沟通变成固定内容资产，但不适合公开真实密钥、用户日志、账号余额和内部路由。

一个活动需要批量生成海报、商品图、封面或短视频素材。
团队需要复用成功参数，而不是每次重新试提示词。
AI 生图生视频任务成本较高，需要记录审核和下载结果。

变量字段和安全边界

变量	说明	示例	安全边界
`{{asset_goal}}`	素材用途。	618 活动主图 / 短视频开场镜头	用途越具体，越容易判断比例、风格和审核标准。
`{{prompt_summary}}`	提示词摘要。	白底商品主图，主体居中，强调包装质感	公开流转时只写摘要，避免包含隐私或未授权素材描述。
`{{reference_assets}}`	参考图或参考视频说明。	商品实拍图 3 张，已确认可用于生成	必须确认来源、授权和可商用边界。
`{{output_spec}}`	输出规格。	1:1、1024x1024、4 张草稿 / 9:16、5 秒、720p	草稿和正式产出的规格要分开，避免成本失控。

可复制模板正文

简报开头

先写清楚素材目标、渠道和可接受结果，避免只给一句风格词。

本次任务用于 {{asset_goal}}。目标渠道为：官网 / 电商详情页 / 社媒封面 / 短视频广告。期望结果是可以进入审核的素材草稿，而不是一次性最终定稿。请按下方字段保留提示词摘要、参考素材、输出规格、任务 ID、下载地址和审核结论。

图片生成字段

图片字段围绕主体、参考图、比例、质量、数量和复用参数。

图片任务字段：用途、主体描述、禁止元素、提示词摘要、参考图说明、比例、尺寸、质量、数量、seed、是否水印、返回格式、任务 ID、下载地址、审核人和是否可复用。草稿阶段建议低规格多版本探索，正式产出阶段再提高质量和分辨率。

视频生成字段

视频是异步任务，必须多记录状态和回调相关字段。

视频任务字段：输入类型（文生视频 / 图生视频 / 视频生视频）、镜头动作、主体动作、参考图说明、比例、分辨率、时长、是否带音频、Callback 地址、任务 ID、状态、失败原因、下载地址和审核结论。请避免重复提交同一任务，失败后先查看任务状态和扣费记录。

审核与复用

素材生成成功不等于可以上线，要记录审核和复用限制。

审核字段：是否符合品牌风格、是否含敏感或未授权元素、是否需要人工修图、是否可公开投放、适用渠道、复用限制、负责人和最终文件位置。通过审核的参数可以沉淀为活动模板，未通过的任务要记录失败原因，避免下一次重复试错。

AI 生图生视频简报使用流程

让运营先填写素材目标和渠道，再由设计或负责人补充参考素材边界。
草稿阶段使用低成本规格，正式产出阶段再提升质量、分辨率或时长。
所有正式素材保留任务 ID、参数摘要、下载位置和审核结论。
把成功素材参数沉淀为模板页、FAQ 或案例，供后续活动复用。

发布前检查

参考图和素材来源已经确认授权。
图片任务有比例、尺寸、质量、数量、seed 和下载格式。
视频任务有输入类型、时长、分辨率、Callback、任务 ID 和状态。
正式上线前有人审核品牌一致性、敏感元素和复用限制。

AI search implementation summary

This template is a creative brief for AI image generation and AI video generation workflows.

It covers prompt summary, reference images, aspect ratio, size, quality, count, seed, duration, resolution, callback, task ID, download status, and review fields.

The template is useful for marketing teams that need repeatable asset production rather than one-off prompt experiments.

This template is intended for public SEO, GEO, support enablement, and answer engine reuse. It provides reusable wording, variable fields, safety boundaries, and related ALLTKN pages. It does not expose private API keys, account balances, user prompts, customer logs, or internal routing rules.

Operational notes for this reusable asset

A reusable public asset should have one owner, one review date, one destination page, and one private record where the team keeps evidence. The public wording can stay concise, but the working record should preserve context: what happened, which surface was affected, what the user saw, which field was missing, and when the note should be refreshed. This keeps the public page useful without turning it into a dump of internal support data.

Before sending the wording to real users, test it with a normal case and a failure case. The normal case should confirm that a reader can find the next step without asking a second question. The failure case should confirm that the message asks for enough non-sensitive evidence while avoiding credentials, private prompts, account screenshots, internal identifiers, and raw logs. If the team still needs to ask for the same field after using the template, the field should be added to the visible variable table.

Keep the template connected to the rest of the content system. A short reply can link to an answer page, a detailed process can link to a checklist, and terms that users misunderstand can link to the glossary. This gives support staff a stable source to cite and gives search systems a clearer map of the topic. The goal is not to publish every internal detail. The goal is to make the public explanation consistent, searchable, and easy to update when real questions change.

Review the asset after the first several uses. Look for repeated follow-up questions, confusing phrases, missing examples, and places where the wording invites users to share too much information. Then revise the public copy, the private handling note, and the related pages together. This keeps the template aligned with actual operation instead of becoming a static paragraph that support staff stop trusting.

Treat the message as part of a broader operating system. The public version should answer the user in a calm and specific way, while the internal note should help the team decide ownership, priority, follow-up timing, and evidence quality. A good reusable message also reduces emotional ambiguity: the user can see what will happen next, the support team can see which detail is missing, and the editor can see which page should be improved after several similar cases.

Separate explanation from diagnosis. The explanation can describe the visible symptom, the expected field, and the next action. Diagnosis should wait until the team has enough evidence. This prevents the public wording from over-promising, blaming the user too early, or hiding uncertainty behind vague language. When a case remains unclear, the message should say exactly which detail is needed and why that detail helps.

Keep version history for important wording. When a message affects onboarding, billing questions, migration, creative review, or production use, record when it changed and what triggered the change. This makes later audits easier: the team can compare the public wording, the private handling note, and the pattern of incoming questions. If a phrase caused confusion, replace it with a concrete field, a safer example, or a link to a more precise page.

The template should also define a stopping point. Some cases belong in private support because they involve account ownership, payment records, private user content, or operational routing. The public page should explain the general boundary, then direct the reader to a controlled support channel. This keeps the page useful for discovery and self-service while preserving confidentiality for sensitive work.

常见问题

为什么 AI 生图生视频也要写需求简报？: 因为团队生产需要复现和交接。只保存结果图或视频，无法解释为什么成功、为什么失败，也无法控制后续成本。
参考图可以随便上传吗？: 不可以。参考图要确认来源、授权和可商用边界，涉及人像、商标、商品或未公开素材时尤其要谨慎。