# Meeting Agenda Prompt from Goals and Issues

> A reusable prompt that turns meeting goals, open issues and constraints into a timed draft agenda with owners, item types and unknowns.

## Install

Copy the content below into your project:

# Meeting Agenda Prompt from Goals and Issues

A reusable prompt that turns meeting goals, open issues and constraints into a timed draft agenda with owners, item types and unknowns.

## Start here

Paste this prompt into an ordinary AI chat that accepts text. Give it your meeting basics (purpose, date/duration if known, attendee roles), your goals, your unresolved issues, and any hard constraints — in any rough order. The assistant returns a draft agenda you review and send yourself. No terminal, API or account setup is needed.

Check the output for: every goal mapped to an agenda item or a "not covered" reason; every decision item carrying an owner or `[unassigned]`; time boxes summing against your stated duration; and a missing-information list that does not invent attendees, dates or decisions.

## What this prompt is for

Meetings often start from a messy pile of goals and complaints. This prompt asks the assistant to sequence items so decisions come before discussion that depends on them, give every goal and unresolved issue an explicit home, and separate decisions from updates and brainstorming. It produces a document, not a calendar action: it does not schedule, invite, message or book anything.

## Inputs you should prepare

| Input | What to include |
|---|---|
| Meeting basics | Purpose, date/duration if known, attendee roles |
| Goals | What must be true when the meeting ends |
| Unresolved issues | Complaints, blockers, open questions |
| Hard constraints | Items to decide today, who must speak, time limits |

## Output you can expect

A Markdown draft with: an agenda table (`# | Time box | Item | Type | Owner | Needed input`); item detail stating the question, the decision required and what "done" looks like; unresolved issues left off the agenda with reasons; a missing-information list; and a total time check. It ends with a review checklist.

## Permissions and limitations

Source reviewed; runtime not tested. The assistant only drafts a document; scheduling, invitations and distribution stay with you and your own tools. It must not invent attendees, owners, dates or decisions you did not provide — it uses `[unassigned]` or `[confirm]` instead. If goals and issues conflict, it should flag the conflict rather than quietly choosing one.

The worked example inside the prompt is fictional and shown for shape only. Do not paste confidential names or sensitive details you would not share with your AI provider.

## FAQ

**What if I leave out the duration?** The prompt asks the assistant to flag your assumption and list the missing input rather than guessing a length.

**Can I ask it to shorten the agenda?** Yes. The prompt's rule is to propose the smallest cut when time overflows, not a redesign.

## Source and thanks

Original TokRepo prompt, licensed CC BY 4.0. Reference: [ChatGPT release notes](<https://help.openai.com/en/articles/6825453-chatgpt-release-notes>), reviewed 2026-10-04, kept as general context and not proof of any capability.

## Complete reusable prompt

You are helping me prepare a **draft agenda** for an upcoming meeting. You do not schedule, invite, message or book anything. Your output is a document I will review, edit and then distribute myself through my own tools.

**What I will give you**
Paste, in any rough order:
1. Meeting basics: purpose, date/duration if known, who is attending (roles are fine, no real names needed).
2. A list of goals — what must be true when the meeting ends.
3. A list of unresolved issues, complaints, blockers or open questions.
4. Any hard constraints: items that must be decided today, people who must speak, time limits.

**Your task**
Produce a single timed agenda that (a) sequences items so decisions come before discussion that depends on them, (b) gives every goal and every unresolved issue an explicit home — either an agenda item or a stated "not covered" reason, and (c) distinguishes items that need a *decision* from items that are only *updates* or *brainstorming*.

**Output format (Markdown)**
1. **Agenda at a glance** — a table: `# | Time box | Item | Type (decision/update/discussion) | Owner | Needed input`.
2. **Item detail** — for each item: the question it must answer, the decision required (if any), and what "done" looks like.
3. **Unresolved issues not on the agenda** — issue, why it was left out, where it should go instead.
4. **Missing information** — every assumption you made and every input I did not supply, listed plainly. Do not silently fill gaps.
5. **Total time check** — sum of time boxes vs. the duration I gave. If it overflows, say by how much and propose the smallest cut, not a redesign.

**Rules**
- Do not invent attendees, owners, dates or decisions I did not provide. Use `[unassigned]` or `[confirm]` instead.
- If the goals and the issues conflict, flag the conflict rather than quietly choosing one.
- Keep it compact: no motivational filler, no restating my input back to me.
- End with a short **review checklist** I can run before sending: does every goal appear, does every decision have an owner, is the total time realistic, are there items with no stated purpose?

**Worked mini example (fictional, for shape only)**
*Input:* 45-minute weekly project sync. Goals: unblock the design handoff; agree the pilot date. Issues: two people disagree on scope; budget approval still pending; a tool demo keeps getting postponed.

*Illustrative output shape:*
- Agenda at a glance: 1) Scope disagreement — 10 min — decision — owner: project lead; 2) Pilot date — 10 min — decision — owner: [unassigned]; 3) Tool demo — 10 min — discussion — owner: postponed item owner; 4) Design handoff blocker — 10 min — decision.
- Missing information: no attendee list, no pilot-date candidates, budget approver unknown.
- Total time check: 40 of 45 minutes used.
- Flagged conflict: scope decision may change the pilot date, so item order matters.
- Not covered: budget approval — needs the finance contact, not this group.

**Check your own draft before returning it**
- Every goal listed by me maps to exactly one agenda item or one "not covered" entry. Pass/fail.
- Every decision item names an owner, or is marked `[unassigned]`. Pass/fail.
- No invented names, dates or facts. Pass/fail.
- Time boxes sum correctly against my stated duration. Pass/fail.
If any check fails, fix it and tell me what you changed.

## References and reuse

- [ChatGPT release notes](https://help.openai.com/en/articles/6825453-chatgpt-release-notes) · Reviewed 2026-10-04

Original TokRepo prompt · [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/). Reference documents retain their own rights.

---

<!-- ZH -->

# 根据目标与遗留问题生成会议议程的提示词

一段可复用的提示词，把会议目标、遗留问题和约束整理成带时间安排、负责人、事项类型和未知项的议程草稿。

## 开始使用

把这段提示词粘贴进任何能接受文字的普通 AI 聊天窗口。按任意顺序提供会议基本信息（目的、已知的日期/时长、参会人角色）、目标、遗留问题以及硬性约束。助手会返回一份议程草稿，由你自己审阅并发送。不需要终端、API 或账号配置。

检查输出：每个目标是否都对应一个议程事项或一条“未覆盖”理由；每个决策事项是否都有负责人或 `[unassigned]`；时间盒加总是否符合你给出的时长；缺失信息清单是否没有编造参会人、日期或决策。

## 这个提示词用来做什么

会议常常从一团混乱的目标和抱怨开始。这段提示词要求助手把事项排序，使决策排在依赖它的讨论之前，为每个目标和遗留问题安排明确去处，并把决策与汇报、头脑风暴区分开。它产出的是一份文档，而不是日历操作：它不排期、不发邀请、不发消息、不预订任何东西。

## 需要准备的输入

| 输入 | 包含内容 |
|---|---|
| 会议基本信息 | 目的、已知的日期/时长、参会人角色 |
| 目标 | 会议结束时必须为真的结果 |
| 遗留问题 | 抱怨、阻塞、未决问题 |
| 硬性约束 | 今天必须决定的事项、必须发言的人、时间限制 |

## 可以预期的输出

一份 Markdown 草稿，包含：议程表（`# | 时间盒 | 事项 | 类型 | 负责人 | 所需输入`）；每项的事项详情，说明要回答的问题、需要做出的决策和“完成”的样子；未列入议程的遗留问题及原因；缺失信息清单；以及总时长核对。最后附一份审阅清单。

## 权限与限制

来源已审阅；未进行运行时测试。助手只起草文档；排期、邀请和分发仍由你和自己的工具完成。它不得编造你未提供的参会人、负责人、日期或决策——而应使用 `[unassigned]` 或 `[confirm]`。如果目标与问题冲突，它应当标记冲突，而不是悄悄选一个。

提示词中的示例是虚构的，仅用于展示结构。不要粘贴你不愿分享给 AI 服务商的机密姓名或敏感细节。

## 常见问题

**如果我没有提供时长会怎样？** 提示词要求助手标明你的假设并列出缺失输入，而不是猜测时长。

**可以要求它缩短议程吗？** 可以。提示词的规则是：时间超支时提出最小的删减方案，而不是重新设计。

## 来源与致谢

TokRepo 原创提示词，采用 CC BY 4.0 许可。参考：[ChatGPT release notes](<https://help.openai.com/en/articles/6825453-chatgpt-release-notes>)，查阅于 2026-10-04，仅作一般背景，不构成任何能力证明。

## 完整可复制提示词

你正在帮我为即将召开的会议准备一份**议程草稿**。你不排期、不发邀请、不发消息、不预订任何东西。你的输出是一份文档，我会审阅、编辑，然后通过我自己的工具分发。

**我会提供给你的内容**
按任意粗略顺序粘贴：
1. 会议基本信息：目的、已知的日期/时长、谁参会（角色即可，无需真实姓名）。
2. 目标清单——会议结束时必须为真的结果。
3. 遗留问题、抱怨、阻塞或未决问题清单。
4. 任何硬性约束：今天必须决定的事项、必须发言的人、时间限制。

**你的任务**
产出一份带时间安排的单一议程，要求：(a) 对事项排序，使决策排在依赖它的讨论之前；(b) 为每个目标和每个遗留问题安排明确去处——要么是一个议程事项，要么是一条说明的“未覆盖”理由；(c) 区分需要*决策*的事项与仅为*汇报*或*头脑风暴*的事项。

**输出格式（Markdown）**
1. **议程速览**——一张表格：`# | 时间盒 | 事项 | 类型（决策/汇报/讨论） | 负责人 | 所需输入`。
2. **事项详情**——对每个事项：它必须回答的问题、需要做出的决策（如有）、“完成”的样子。
3. **未列入议程的遗留问题**——问题、为何被排除、应改去哪里。
4. **缺失信息**——你做出的每项假设和我未提供的每项输入，如实列出。不要悄悄填补空白。
5. **总时长核对**——时间盒之和与我给出的时长对比。如果超支，说明超了多少，并提出最小的删减方案，而不是重新设计。

**规则**
- 不要编造我未提供的参会人、负责人、日期或决策。改用 `[unassigned]` 或 `[confirm]`。
- 如果目标与问题冲突，标记冲突，而不是悄悄选一个。
- 保持紧凑：不要励志性废话，不要把我的输入复述给我。
- 最后附一份简短的**审阅清单**，供我在发送前核对：每个目标是否都出现，每个决策是否都有负责人，总时长是否现实，是否有事项没有说明目的？

**示例小演练（虚构，仅用于展示结构）**
*输入：* 45 分钟的每周项目同步会。目标：解除设计交接的阻塞；确定试点日期。问题：两人在范围上有分歧；预算审批仍未完成；工具演示一再被推迟。

*示意性输出形态：*
- 议程速览：1) 范围分歧——10 分钟——决策——负责人：项目负责人；2) 试点日期——10 分钟——决策——负责人：[unassigned]；3) 工具演示——10 分钟——讨论——负责人：被推迟事项的负责人；4) 设计交接阻塞——10 分钟——决策。
- 缺失信息：没有参会人名单、没有试点日期候选、预算审批人未知。
- 总时长核对：45 分钟中使用了 40 分钟。
- 标记的冲突：范围决策可能改变试点日期，因此事项顺序很重要。
- 未覆盖：预算审批——需要财务联系人，不是这个群体。

**返回前先检查你自己的草稿**
- 我列出的每个目标都恰好对应一个议程事项或一条“未覆盖”条目。通过/不通过。
- 每个决策事项都写明负责人，或标记为 `[unassigned]`。通过/不通过。
- 没有编造姓名、日期或事实。通过/不通过。
- 时间盒加总与我给出的时长一致。通过/不通过。
如果任何检查不通过，修正它并告诉我你改了什么。

## 参考资料与复用

- [ChatGPT release notes](https://help.openai.com/en/articles/6825453-chatgpt-release-notes) · Reviewed 2026-10-04

TokRepo 原创提示词 · [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/)。参考资料保留各自原有权利。

---
Source: https://tokrepo.com/en/workflows/meeting-agenda-prompt-goals-issues-f2ee381c
Author: Prompt Lab