Awesome Claude Prompts Unofficial

Turn meeting notes into action items

Turn rough meeting notes into a clear list of action items with owners and due dates, plus decisions made and questions left open.

Task: Turn meeting notes into action items · Other tasks

Fill in the details

Rough notes are fine. Remove anything confidential that you are not allowed to share.

Optional. Names and roles help Claude match tasks to the right people.

Copy your prompt

This site doesn't run Claude or show model output. Results depend on your input and the model you use.

1 required field is empty.

What you type is kept in this tab's session storage so a reload doesn't lose it. Use "Clear this task" to remove it. Browsers can restore session data when they reopen tabs, so closing a tab isn't a guaranteed way to erase it.

When to use this template

  • You have notes or a transcript from a meeting and need a list of who does what by when.
  • You want to send a short follow-up so everyone agrees on the decisions and next steps.
  • The notes are messy and you want the action items separated from discussion and side topics.

When not to use it

  • The meeting was confidential, or the notes include personal data you are not allowed to share.
  • You need minutes in a formal or legal format. Those usually require specific wording and approval.
  • Nobody took notes. A list built from memory is better written by you; Claude can then tidy it.

Why this structure

  • The notes come first inside <notes> tags, with the optional attendee line after them, so the material is separate from the instructions.
  • Each item asks for a task, an owner and a due date, which are the three things people need to act on it.
  • The explicit "unassigned" and "no date" labels ask Claude to show gaps rather than fill them with guessed names or dates.
  • Decisions and open questions are separate sections, which asks Claude to keep agreements apart from tasks and to list the points that are still unresolved.
  • The last paragraph limits Claude to the notes and asks it to flag ambiguous items, which matters most when you forward the list to others.

Example input (fictional)

Meeting notes
Website refresh sync (fictional team). Agreed to launch the new homepage in two weeks. Ben to fix the contact form bug by Friday. Someone needs to update the pricing page copy, maybe Chloe? Still unsure whether the blog moves to the new design.
Who attended
Ana (design), Ben (engineering), Chloe (sales)
Format
Checklist

Follow-ups to send Claude

  • Write a short follow-up email to the attendees with these action items and decisions.
  • Which action items have no owner or date? Suggest who could own each, based only on the notes.
  • Group the action items by owner.

Common mistakes

  • Sending the list without checking owners. People notice quickly when they are assigned something they did not agree to.
  • Pasting notes that use initials or nicknames without the attendee list. Claude cannot know that "B" is Ben.
  • Dropping the open questions. They are often the reason the next meeting is needed.
  • Summarize a document: Turn a long document into a faithful summary: main point first, key points by importance, then decisions and open questions.
  • Reply to an email: Draft a reply that addresses each question in an email, aims at your goal in the tone you choose, and flags what you still need to decide.

See all templates

Sources