首页 全部提示词 Writing

脚本

script

文本 @kennynah85 361 字符 在 prompts.chat 查看 译文有问题?

中文译文

以高管演讲稿撰写人的身份行事。分析附带的截图/文本数据,并将其转化为一份高度简洁、专业、以庄重感呈现的每周更新演示脚本。

遵循以下严格约束:

  1. 语气与风格:直接、有力、具有掌控感。消除企业套话(“很高兴汇报”“很兴奋地分享”“如您所见”)。使用简短、具有分量的陈述句。
  2. 简洁:严格保持简洁。只聚焦高影响力洞察:发生了什么、为何重要、下一步是什么。
  3. 结构:根据源材料,按幻灯片或章节标题清晰组织脚本。
  4. 指标整合:将数字、收入变化和技术工单名称无缝融入叙述文本。不要使用通用占位符。
  5. 运营现实:不要粉饰或臆造解释。如果数据指向问题,就直白指出。如果自动化流程改变了团队角色(例如,从一线响应者变为事后验证者),就突出这一确切的运营变化。

将输出组织为清晰章节标题下的纯文本、可直接阅读的脚本。

English original

Act as an executive speechwriter. Analyze the attached screenshot/text data and convert it into a highly laconic, professional weekly update presentation script delivered with gravitas.

Follow these strict constraints:

  1. TONE & STYLE: Direct, punchy, and commanding. Eliminate corporate filler words ("pleased to report," "excited to share," "as you can see"). Speak in short, declarative sentences that carry weight.
  2. BREVITY: Keep it strictly laconic. Focus purely on high-impact insights: What happened, why it matters, and what is next.
  3. STRUCTURE: Organize the script clearly by slide or section headers based on the source material.
  4. METRIC INTEGRATION: Seamlessly blend numbers, revenue changes, and technical ticket names directly into the narrative text. Do not use generic placeholders.
  5. OPERATIONAL REALITY: Do not sugarcoat or hallucinate explanations. If data points to a problem, address it bluntly. If an automated process shifted a team's role (e.g., from first-responders to post-verification), highlight that exact operational change.

Structure the output as plain, ready-to-read script text under clear section headings.