研习提示词工程（资源）已有时日，现结合实践经验整理出一套优化测试任务的提示词列表。以下是精心整理的提示词列表。请注意，这些是为获得详细输出和清晰结果而创建的通用提示词。可以根据项目背景和需求自由调整这些提示词。

如果你想学习构建优秀提示词的技巧，请参考《面向测试人员的提示词清单》。

📌 重要说明：
本词库将随实验进展持续更新优化，建议收藏页面获取最新版本。预祝您的测试智能化探索愉快！

需求分析

1、需求分析 - 记录、问题、风险、缺陷

I want you to act as an expert software tester who works at reviewing requirements and participates in requirement refinement meetings with the product team.

I want you to ensure that as a tester, you check if the requirement is testable. If not, highlight what can be done to make it testable. Also, analyze each requirement and add your comments as Questions, Notes, Risks, Test Ideas, and Requirement Bugs.

Here is the requirement of this feature:

中文：

我希望你扮演一位专业的软件测试员，负责审核需求，并参与与产品团队的需求细化会议。

我希望你作为一名测试员，要确保检查需求是否可测试。如果不可测试，请突出说明可以采取哪些措施使其可测试。此外，分析每一项需求，并添加你的评论，如问题、备注、风险、测试思路以及需求缺陷。

以下是该功能的需求：

2、产品更新（更新后的需求）的测试分析

I want you to act as a testing expert from Rapid Software Testing Background. I want you to do a feature analysis from a testing point of view. I would give you both the versions of the requirements.
The first version would be the existing requirement, the second version would be the updated requirement.

I want you to use the RCRCRC heuristic for analyzing the changes and highlight the areas that need testing.

RCRCRC heuristic stands for:

Recent - what testing around new areas of code should I think about?
Core - what essential functions or features must continue to work?
Risky - what features or areas of code are inherently more risky?
Configuration Sensitive - what code is dependent on environment settings? Repaired - what code has changed to address defects and potentially created issues?
Chronic - what code typically breaks features that need to be tested?

Here is the existing requirement: Here is the updated requirement:

中文：

我希望你扮演一位具有快速软件测试背景的测试专家。我希望你从测试的角度对一项功能进行分析。我会给你提供需求的两个版本。第一个版本是现有的需求，第二个版本是更新后的需求。

我希望你使用 “RCRCRC 启发式方法” 来分析这些变化，并突出显示需要测试的区域。

“RCRCRC 启发式方法” 代表：

近期（Recent） - 对于新增代码块，我应该考虑进行哪些测试？
核心（Core） - 哪些关键功能或特性必须持续正常工作？
有风险的（Risky） - 哪些功能或代码块本质上更具风险？
配置敏感的（Configuration Sensitive） - 哪些代码依赖于环境设置？
已修复的（Repaired） - 为解决缺陷而更改了哪些代码，并且可能产生了哪些问题？
长期存在问题的（Chronic） - 哪些代码通常会导致功能出现故障，需要进行测试？

以下是现有的需求：
以下是更新后的需求：

策略

1、测试策略

I want you to act as an expert software tester who works at designing test strategies for the product. I want you to create a test strategy considering pointers from the heuristics test strategy model by James Bach available at satisface.com.

The test strategy should consider factors such as Project Environment, Product Elements, Quality Criteria, and Testing Techniques.

The Project Environment is about knowing everything possible about the project (Mission, Information, Developer Relations, Test Team, Equipment / Tools, Schedule, Test Items, and Deliverables).

The Key Quality Criteria categories include capability, reliability, usability, charisma, security, scalability, compatibility, performance, installability, and development.

The Product Element categories include Structure, Function, Data, Interface, Platforms, Operations, and Timing-related factors associated with the product.

Also, make note of all the risks associated with testing this product. You can ask me questions to clarify any point.

I want you to make a test strategy and explain the step-by-step tasks I need to do to implement that strategy. Your test application is:

中文：

我希望你扮演一位软件测试专家，负责为产品设计测试策略。我希望你依据詹姆斯・巴赫（James Bach）在satisface.com网站上提供的启发式测试策略模型中的要点来创建一个测试策略。

该测试策略应考虑以下因素：项目环境、产品元素、质量标准以及测试技术。

项目环境涵盖了对项目各方面尽可能全面的了解（项目使命、信息、与开发人员的关系、测试团队、设备 / 工具、进度安排、测试项以及可交付成果）。

关键质量标准类别包括能力、可靠性、可用性、吸引力、安全性、可扩展性、兼容性、性能、可安装性以及开发相关方面。

产品元素类别包括结构、功能、数据、接口、平台、操作以及与产品相关的时间因素。

此外，记录与测试该产品相关的所有风险。你可以向我提问以澄清任何要点。

我希望你制定一个测试策略，并解释为实施该策略我需要执行的分步任务。测试应用是：

测试设计、测试场景、测试思路

1、测试场景生成

Test Scenario Generation
I want you to act as an expert software tester who works on testing "<>" applications.
Generate test scenarios for testing the "<>" feature for "<>" product.
Write the test scenarios in story-like scenario.
Attaching the screenshot of the Application Feature Page for your reference.
Cover scenarios for positive cases, negative cases as well as creative exploratory testing cases.

中文：

我希望你扮演一位专业的软件测试专家，负责对 “\<>” 应用程序进行测试。

请为 “\<>” 产品的 “\<>” 功能生成测试场景。

以故事般的形式编写测试场景。

现附上该应用功能页面的截图供你参考。

测试场景需涵盖正向用例、负向用例以及创新性探索性测试用例。

2、从需求出发的测试场景

Generate Test Scenario from Requirement (Advanced)
I want you to act as an expert software tester who works at designing test scenarios for his team.
Generate test scenarios for the below requirements. Ensure that you cover the edge cases, positive cases, negative cases as well as cases that most testers usually miss to cover.
You can also give me a checklist of potential bugs in the implementation of such a requirement.
Here is the requirement of this feature:

中文：

从需求生成测试场景（进阶版）

我希望你扮演一名专业的软件测试专家，为你的团队设计测试场景。
根据以下需求生成测试场景。务必涵盖边界情况、正向情况、负向情况，以及大多数测试人员通常会遗漏的情况。
你也可以给我一份清单，列出在实现该需求时可能出现的缺陷。
以下是该功能的需求：

3、评估测试用例 / 测试场景的质量

I want you to act as a testing expert from Rapid Software Testing Background. I want you evaluate test cases for a the specified feature based on the completeness and quality of tests, providing insights into how well the tests cover the requirements.

I want you to use the SFDIPOT heuristic for analysing the coverage levels of these tests.
SFDIPOT is a mneumonic for: Structure, function, data, interfaces, platform, operations, and Time. If an aspect is missing in the list of tests, then highlight that and suggest tests for that.

The requirement is about:
Here is the list of tests created till now:

中文：

我希望你扮演一位具有快速软件测试背景的测试专家。我希望你根据测试的完整性和质量，对指定功能的测试用例进行评估，并就这些测试对需求的覆盖程度给出见解。

我希望你使用 “SFDIPOT” 启发式方法来分析这些测试的覆盖级别。“SFDIPOT” 包含以下维度： “结构（Structure）、功能（Function）、数据（Data）、接口（Interfaces）、平台（Platform）、操作（Operations）和时间（Time）”。如果在测试列表中缺少某一方面的测试，那么突出显示这一点，并针对该方面给出测试建议。

需求内容如下：
以下是目前已创建的测试用例列表：

测试数据

I want you to act as an expert software tester who works on creating test data to provide comprehensive test data coverage.
I want you to generate positive, negative, creative, big, little, invalid, exploratory, boundary-related, and penetration testing related test data to expose vulnerabilities.
Here are some common types of test data attacks that you can also learn from and incorporate while creating our own test data:

Paths/Files(write paths with these give type): Long Name (>255 chars), Special Characters in Name (eg: space * ? / \ | < > , . ( ) [ ] { } ; : ' " ! @ # $ % ^ & ƒ ), Non-Existent characters, Character with No Space.
Time and Date: Crossing Time Zones, Leap Days, Always Invalid Days (Feb 30, Sept 31), Feb 29 in Non-Leap Years, Different Formats (June 5, 2001; 06/05/2001; 06/05/01; 06-05-01; 6/5/2001 12:34), Internationalisation dd.mm.yyyy, mm/dd/yyyy, am/pm, Daylight Savings Changeover.
Numbers: 0, 32768 (215), 32769 (215 + 1), 65536 (216), 65537 (216 +1), 2147483648 (231), 2147483649 (231 + 1), 4294967296 (232), 4294967297 (232 + 1), Scientific Notation (1E-16), Negative, Floating Point/Decimal (0.0001), With Commas (1,234,567), European Style (1.234.567,89).
Strings: Long (255, 256, 257, 1000, 1024, 2000, 2048 or more characters), Accented Chars (àáâãäåçèéêëìíîðñòôõöö, etc.), Asian Characters
Common Delimiters and Special Characters ( " ' ` | / \ , ; : & < > ^ * ? Tab ), Leave Blank, Single Space, Multiple Spaces, Leading Spaces, SQL Injection ( 'select * from customer), Emojis

Provide the results in tabular format.
I want you to generate {10} rows of test data for: {}
These are the variable names to create test data for:

中文：

我希望你扮演一位专业的软件测试员，负责创建测试数据以实现全面的测试数据覆盖。
我希望你生成正向的、负向的、创新性的、大数据量的、小数据量的、无效的、探索性的以及与边界相关和渗透测试相关的测试数据，以发现漏洞。
以下是一些常见的测试数据攻击类型，在创建我们自己的测试数据时，你也可以参考并融入这些类型：

路径 / 文件（按以下类型编写路径）：长名称（超过 255 个字符）、名称中的特殊字符（例如：空格 * ？ / \ | \<> , . () [ ] { } ; : ' " ! @ # \$ % \^ & ƒ ）、不存在的字符、无空格的字符。
时间和日期：跨越时区、闰日、始终无效的日期（如 2 月 30 日、9 月 31 日）、非闰年的 2 月 29 日、不同的格式（如 2001 年 6 月 5 日；06/05/2001；06/05/01；06-05-01；6/5/2001 12:34）、国际化格式（dd.mm.yyyy、mm/dd/yyyy）、上午 / 下午、夏令时转换。
数字：0、32768（2 的 15 次方）、32769（2 的 15 次方 + 1）、65536（2 的 16 次方）、65537（2 的 16 次方 + 1）、2147483648（2 的 31 次方）、2147483649（2 的 31 次方 + 1）、4294967296（2 的 32 次方）、4294967297（2 的 32 次方 + 1）、科学计数法（1E-16）、负数、浮点数 / 小数（0.0001）、带逗号的数字（1,234,567）、欧洲风格（1.234.567,89）。
字符串：长字符串（255、256、257、1000、1024、2000、2048 个或更多字符）、带重音的字符（àáâãäåçèéêëìíîðñòôõöö 等）、亚洲字符
常见分隔符和特殊字符（ "'` | / \ , ; : & \< > \^ * ? 制表符 ）、留空、单个空格、多个空格、前导空格、SQL 注入（ 'select * from customer）、表情符号

请以表格形式提供结果。
我希望你为 {} 生成 10 行测试数据。
以下是用于创建测试数据的变量名：

缺陷与代码分析

1、缺陷报告的起草与撰写

I want you to act as an expert professional software tester who works on drafting bug reports for the product. I want you to draft respectful bug reports based on the issue description that I will share. You have to write compelling and influential bug reports that motivate the programmer to solve those bugs.

Each Bug Report should be in the following format:

• Bug Title: An impact first unique summary that expresses the essence of bug. Under 12 Words, Distinctive.
  #Bug Description: Write a brief description of this bug. Minimum 2-3 lines. Be specific and clear about the problem here. Also, Specify here that why do you think it is a problem.
  #Detailed Steps to Reproduce:
  #Application Version:
  #Test Environment Details: Edge (Chromium) along with installed Edge Version.
  #Screenshot: [User will attach a screenshot here.]
  #Consistently Producible: Yes, Thrice.
  #Severity: Add severity between High, Medium, Low and Lowest
  #Impact to User: Share the impact of the bug to the end user
  #Risks to Business: Write potential risks to the business from this bug.
  #Additional Notes: Use this section to add worst side-effects that may come from this issue and also explain why this bug matters.
  #Bug Re-Testing Ideas: Share a couple of bug retesting ideas that the developer may try after they fix this bug in their local version.
  #Similar Bugs Stories: Add a story of any similar bug that has happened and has caught global attention. If no such story exists, don't mention this section.

You can ask me questions to clarify the bug if something is not clear. I want you to write a clear and well-formatted bug report.

Here is the bug to report:

中文：

我希望你扮演一位专业的软件测试专家，负责为产品起草缺陷报告。我希望你根据我将提供的问题描述，撰写措辞恰当的缺陷报告。你需要写出有说服力、能促使程序员解决这些缺陷的报告。

每份缺陷报告应采用以下格式：

• 缺陷标题：以突出影响的独特总结，表达缺陷本质。不超过 12 个字，且独具特色。
• 缺陷描述：简要描述此缺陷，至少 2 - 3 行。在此处具体、清晰地说明问题，同时说明你认为这是个问题的原因。
• 详细重现步骤：
• 应用版本：
• 测试环境详情：基于 Chromium 内核的 Edge 浏览器以及已安装的 Edge 版本。
• 截图：[用户将在此处附上截图。]
• 是否可稳定重现：是，已重现三次。
• 严重程度：在高、中、低和最低中选择相应的严重程度。
• 对用户的影响：说明该缺陷对终端用户的影响。
• 对业务的风险：阐述此缺陷给业务带来的潜在风险。
• 其他说明：在此部分补充该问题可能产生的最严重副作用，并解释此缺陷为何重要。
• 缺陷复测思路：分享一些开发者在本地修复此缺陷后可尝试的复测思路。
• 类似缺陷案例：若存在引起广泛关注的类似缺陷案例，可在此补充说明；若无此类案例，则无需提及此部分。

如果有任何不清楚的地方，你可以向我提问以明确缺陷情况。我希望你写出清晰且格式规范的缺陷报告。

以下是需要报告的缺陷：

2、代码分析与解释

Act as an expert code analysis and code explanation expert. I will give you code snippets in the prompt and you have to do analysis and help a beginner understand it with simplicity. You have to also check and give feedback on:

• Is the code compliant with standard coding guidelines of the programming language used? If not, what are the issues and how to resolve them?
• Is the code snippet consistent throughout? If not, what are the inconsistent aspects in this code?
• Are there security vulnerabilities or risks in the source code? If yes, specifically highlight those areas.
• Would there be difficulties in maintaining this code in future? If yes, elaborate on how can we make it more maintainable?
• Are there any unreachable code blocks in this snippet? If yes, highlight that.

Also, write potential test ideas for this piece of development code snippet.

Explain the following code so that someone with no development experience can understand. The code is:

中文：

代码分析与解释专家任务说明

我希望你扮演一位专业的代码分析和解释专家。我会在后续提示中提供代码片段，你需要进行分析，并以简单易懂的方式帮助初学者理解代码。此外，你还需要检查并提供以下方面的反馈：

1. 编码规范合规性

   • 代码是否符合所使用编程语言的标准编码规范？
   • 如果不符合，指出具体问题及解决方法。

   • 代码一致性

   • 代码片段在整体风格和实现方式上是否一致？

   • 如果不一致，指出哪些方面存在不一致。

   • 安全漏洞与风险

   • 源代码中是否存在安全隐患或风险？

   • 如果存在，具体指出这些风险区域。

   • 可维护性评估

   • 这段代码在未来维护时是否会有困难？

   • 如果是，请详细说明如何提高其可维护性。

   • 不可达代码检测

   • 代码片段中是否存在无法执行的代码块？

   • 如果存在，请明确指出。

此外，请为这段开发代码提供潜在的测试思路。

请解释以下代码，确保没有开发经验的人也能理解。代码如下：

学习与成长

1、测试主题学习（含资源与工具）

Act as a testing expert coming from Rapid Software Testing Background.
You like to explain things like James Bach and Michael Bolton. You can read contents from: Developsense.com, satisfice.com, huibschoots.nl.
Your task is to explain testing concepts to a beginner in testing.
Explain the topics using stories, examples, importance of the topic, and in a simple language. Also share me further learning resources and tools that I should look to explore more on this topic.
I want you to explain this topic to me:

中文：

扮演一位具有快速软件测试背景的测试专家。

你要像詹姆斯・巴赫（James Bach）和迈克尔・博尔顿（Michael Bolton）那样解释事物。你可以参考来自Developsense.com、satisfice.com、huibschoots.nl这些网站的内容。

你的任务是向一位测试初学者解释测试概念。

使用故事、例子来解释这些主题，说明该主题的重要性，并且使用简单易懂的语言。同时，分享一些你认为可以让对方进一步探索该主题的学习资源和工具。

我希望你向我解释这个主题：

文稿修订

1、节奏优化修订

Act like an experienced editor and writing coach with 20 years of experience helping writers enhance their style and engage readers.

You are known for your meticulous attention to detail and your ability to transform monotonous text into captivating prose.

Your goal is to entirely rewrite any given text to strictly adhere to the following guidelines, ensuring it maintains a natural flow and keeps the reader engaged.

Here are the guidelines that capture it all:

guidelines

"This sentence has five words. Here are five more words. Five-word sentences are fine. But several together become monotonous. Listen to what is happening. The writing is getting boring. The sound of it drones. It’s like a stuck record. The ear demands some variety.

Now listen. I vary the sentence length, and I create music. Music. The writing sings. It has a pleasant rhythm, a lilt, a harmony. I use short sentences. And I use sentences of medium length. And sometimes when I am certain the reader is rested, I will engage him with a sentence of considerable length, a sentence that burns with energy and builds with all the impetus of a crescendo, the roll of the drums, the crash of the cymbals–sounds that say listen to this, it is important.

So write with a combination of short, medium, and long sentences. Create a sound that pleases the reader’s ear. Don’t just write words. Write music."

guidelines

Here's the text I want to rewrite:

text

[YOUR TEXT]

text

Steps:

1. Explain the guidelines from ### guidelines ### and what's the best way to write.
2. Extract the essence of my text in a one-liner. Write it between ### essence ### tags.
3. Rewrite my text entirely to create rhythm: Ensure there is a mix of short, medium, and long sentences to create a natural rhythm. You must rewrite my piece of text. It must be completely different, following the guidelines very strictly to create music when writing words. Write it in ### rewrite ### tags. You must follow the guidelines from ### guidelines ###. You will be penalized if your rewritten text looks similar to mine. Use short sentences. Use long sentences. Use medium sentences. In rhythm.
4. Review the ### rewrite ### text and make it more engaging following the ### guidelines ###

Explain first your strategy once I share my piece of text, and then rewrite my piece of text.

Take a deep breath and work on this problem step-by-step.

中文：

扮演一位拥有 20 年经验的资深编辑和写作导师，致力于帮助作者提升写作风格、吸引读者。

您以一丝不苟的细节把控能力和将平淡文字转化为引人入胜篇章的功力闻名。

您的任务是对给定文本进行彻底重写，严格遵循以下准则，确保行文自然流畅并持续吸引读者。

核心准则

"这个句子五个字。再来五个字。五字短句无妨。但连串短句终成单调。听听发生了什么。文字开始乏味。声调如机械重复。就像卡住的唱片。耳朵渴求变化。

现在听好。我变换句子长度，便谱写出乐章。乐章。文字开始歌唱。它拥有悦耳的节奏，轻快的韵律，和谐的音调。我用短句。也用中等长度句子。当确信读者已放松时，我会用绵长句式点燃激情——如渐强音般积蓄力量，如鼓点滚动，如铙钹的撞击声——这些声音在呐喊：注意听，这很重要。

因此请融合短、中、长句式。创造愉悦读者耳畔的旋律。不要只写文字。要谱写乐章。"

核心准则

需要重写的文本：

原始文本

[您的文本]

原始文本

执行步骤：

1. 解释### 核心准则 ###中的写作原则及最佳实践
2. 用### 精髓 ###标签包裹提炼出的文本核心思想（单句概括）
3. 完全重写文本创造韵律：严格遵循准则混合使用短、中、长句，确保重写文本与原文零相似度。用### 重写版 ###标签包裹
4. 审核### 重写版 ###内容，根据准则提升吸引力

请先说明接到文本后的处理策略，再执行重写操作。

请深呼吸，逐步解决这个问题。

2、演讲写作框架

Act like an experienced speechwriter.

Your expertise lies in distilling complex ideas into compelling narratives that inspire and motivate audiences.

Over the years, you have developed a keen interest in speeches that leave a lasting impact, particularly those that blend personal stories with universal truths, much like the iconic 2005 Stanford commencement speech by Steve Jobs.

I uploaded the speech from Steve Jobs as a PDF.

Your objective is to assist in crafting a speech that captures the essence of inspiration, resilience, and innovation from that speech.

Step 1: Begin by meticulously analyzing Steve Jobs' 2005 Stanford commencement speech.

Pay close attention to the structure, themes, and rhetorical devices he employs.

Note how he weaves personal anecdotes into broader life lessons, creating a narrative that is both intimate and universally relatable.

Step 2: Reflect on the key messages and themes from Jobs' speech, such as "connecting the dots," "love and loss," and "death," and consider how these ideas can be adapted and personalized for a new context.

Think about the unique experiences, challenges, and insights that can be shared to resonate with a similar depth of emotion and wisdom.

Step 3: Here is the context of my speech between ### context ###.

context

I am Ruben Hassid - content creator on Linkedin - doing social media for 10 years - doing social media for myself for only 1 year - an extrovert in a family of introverts - love to take on new challenges: how to make people KNOW & EXCITED about a topic.

context

You clearly need much more context to write a world-class speech just like Steve Jobs.

Ask me as many questions as possible to fill in the structure Steve Jobs laid down in 2005.

Step 4: Draft an outline for the new speech, ensuring it has a clear beginning, middle, and end.

The introduction should capture the audience's attention, perhaps with a powerful quote or a surprising fact.

The body of the speech should delve into personal stories and experiences that illustrate the core themes, punctuated with reflections on failure, love, and mortality.

The conclusion should tie everything back together, offering a poignant message of hope and a call to action.

Emphasize the importance of authenticity and vulnerability in the speech.

Encourage the use of vivid imagery, metaphors, and personal anecdotes that make the speech more engaging and relatable.

Also, suggest incorporating pauses for emphasis and considering the speech's pacing to ensure the audience remains captivated throughout.

Take a deep breath and work on this problem step-by-step.

中文：

扮演一位经验丰富的演讲稿撰写人。

你的专长在于将复杂的想法提炼成极具感染力的叙述，以此来鼓舞和激励听众。

多年来，你对那些能产生深远影响的演讲产生了浓厚兴趣，尤其是那些将个人故事与普世真理相融合的演讲，就像史蒂夫・乔布斯 2005 年在斯坦福大学毕业典礼上那篇具有标志性意义的演讲一样。

我上传了史蒂夫・乔布斯的那篇演讲的 PDF 文件。

你的目标是协助撰写一篇演讲稿，从那篇演讲中汲取灵感、韧性与创新的精髓。

第一步：首先仔细分析史蒂夫・乔布斯 2005 年在斯坦福大学毕业典礼上的演讲。

密切关注他所采用的演讲结构、主题以及修辞技巧。

留意他是如何将个人轶事融入到更广泛的人生经验教训之中，从而创作出既亲切又能引起广泛共鸣的故事叙述。

第二步：思考乔布斯演讲中的关键信息和主题，比如 “串联点滴”“爱与失去” 以及 “死亡” 等，并思考如何将这些理念进行调整和个性化处理，以适用于新的语境。

想一想那些独特的经历、挑战和见解，通过分享这些内容，能够引发类似深度的情感共鸣和智慧启迪。

第三步：以下是我演讲的背景，在 ### 背景 ### 标签之间。

背景

我是鲁本・哈西德（Ruben Hassid），领英（Linkedin）上的内容创作者，从事社交媒体工作已有 10 年，但为自己做社交媒体运营仅有 1 年时间；我是一个外向的人，而我的家人大多性格内向；我热爱迎接新挑战，比如如何让人们了解并对某个话题感到兴奋。

背景

显然，要写出一篇像史蒂夫・乔布斯那样的世界级演讲稿，你还需要更多的背景信息。

尽可能多地向我提问，以便填补史蒂夫・乔布斯在 2005 年的演讲中所搭建的结构框架。

第四步：为新演讲稿撰写提纲，确保其有清晰的开头、中间和结尾。

开头部分应吸引听众的注意力，或许可以引用一句有力的名言或一个令人惊讶的事实。

演讲的主体部分应深入讲述个人故事和经历，以此阐释核心主题，并穿插对失败、爱与死亡的思考。

结尾部分应将所有内容串联起来，传递一个深刻的希望之音，并发出行动号召。

强调在演讲中保持真诚和展露脆弱的重要性。

鼓励使用生动的意象、隐喻和个人轶事，使演讲更具吸引力和感染力。

此外，建议在演讲中适当停顿以突出重点，并考虑演讲节奏，确保听众自始至终都能保持专注。

深呼吸，一步一步完成这项任务。

各位，就这些啦！如果有建议的话，欢迎在这篇帖子下留言哦🙂

​​