Meeting Agenda Prompt from Goals and Issues

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

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.

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 · Reviewed 2026-10-04

Original TokRepo prompt · CC BY 4.0. Reference documents retain their own rights.