Meeting notes to actions

pacpio-team/meeting-notes-to-actions
Copy project link
Public
Anyone can see and download this project, even without signing in.
Owner: Pacpio Team Made by the Pacpio team
Made by the Pacpio team
Report

Use it with your AI

Works in Claude, ChatGPT or any other AI

  1. Step 1: Connect your AI

    Do it once. It takes a minute.

    Connect your AI

  2. Step 2: Ask your AI

    Paste this into your chat:

    What does the Pacpio project pacpio-team/meeting-notes-to-actions do?

Make a copy Sign in to get your own project to change. Download a copy All files in one ZIP. The copy doesn’t update by itself.

meeting-record-example.md

1.6 KB · 32 lines
Copy the text
Download this file

Example: meeting record

Input

"Team meeting today, 22 Oct. Me, Olga (design), Tom (sales), Priya (support). Launch moved to 15 Nov, everyone agreed. Olga will send the final banners by 5 Nov. Tom asked whether we discount for early birds, no answer, Priya will check with finance. Priya: support hours before launch need a decision, she'll draft options. I need to write the launch email, by 10 Nov. Tom wants a dry run on 12 Nov, agreed. Next meeting Tuesday 29 Oct."

Result (meetings/2026-10-22-team-meeting.md)

Participants: Anna (lead, record), Olga (design), Tom (sales), Priya (support).

Overview: the team moved the launch to 15 November and set the work before it. Four action items, one open question for finance.

Decisions:

  • Launch date is 15 November (all).
  • Dry run on 12 November (all).

Action items:

# Action Owner Due Status
12 Send the final banners Olga 5 Nov open
13 Check with finance whether early-bird discounts are possible Priya no date open
14 Draft options for support hours before launch Priya no date open
15 Write the launch email Anna 10 Nov open

Open questions:

  • Early-bird discount: yes or no? (Priya, after talking to finance)

Key points:

  • Launch moved from the earlier date to 15 November.
  • Support hours before launch still need a decision.

Next meeting: Tuesday 29 October.

Chat answer: "Record saved. Two decisions: launch 15 Nov, dry run 12 Nov. Four new action items (#12 to #15), two without a date. Unclear: nothing. Saved to meetings/2026-10-22-team-meeting.md; actions.md updated."

# Example: meeting record## Input"Team meeting today, 22 Oct. Me, Olga (design), Tom (sales), Priya (support). Launch moved to 15 Nov, everyone agreed. Olga will send the final banners by 5 Nov. Tom asked whether we discount for early birds, no answer, Priya will check with finance. Priya: support hours before launch need a decision, she'll draft options. I need to write the launch email, by 10 Nov. Tom wants a dry run on 12 Nov, agreed. Next meeting Tuesday 29 Oct."## Result (meetings/2026-10-22-team-meeting.md)Participants: Anna (lead, record), Olga (design), Tom (sales), Priya (support).Overview: the team moved the launch to 15 November and set the work before it. Four action items, one open question for finance.Decisions:- Launch date is 15 November (all).- Dry run on 12 November (all).Action items:| # | Action | Owner | Due | Status ||---|---|---|---|---|| 12 | Send the final banners | Olga | 5 Nov | open || 13 | Check with finance whether early-bird discounts are possible | Priya | no date | open || 14 | Draft options for support hours before launch | Priya | no date | open || 15 | Write the launch email | Anna | 10 Nov | open |Open questions:- Early-bird discount: yes or no? (Priya, after talking to finance)Key points:- Launch moved from the earlier date to 15 November.- Support hours before launch still need a decision.Next meeting: Tuesday 29 October.Chat answer: "Record saved. Two decisions: launch 15 Nov, dry run 12 Nov. Four new action items (#12 to #15), two without a date. Unclear: nothing. Saved to meetings/2026-10-22-team-meeting.md; actions.md updated."