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.

README.md

2.7 KB · 38 lines
Copy the text
Download this file

Meeting notes to actions

For anyone who runs or sits in meetings: a team lead, a project coordinator, a board member, a parents' council. After the meeting there are rough notes or a transcript, and a week later nobody remembers who promised what. This project turns your notes into a clean record in one format, keeps a single list of action items across all your meetings, prepares the next agenda from what is still open, and writes the message to participants.

How to start

  1. Make a copy of this project (the "Make a copy" button).
  2. Connect your AI to Pacpio if you have not yet.
  3. Ask: "Here are my notes from today's team meeting, make a record and update the action list", and paste your notes.

The first time, your assistant asks three questions: which team and meetings, who takes part, and in which language to keep records. It saves the answers in my/team.md.

What is inside

  • AGENTS.md — how your assistant works here: an action item is something a named person agreed to do, nothing is attributed that the notes do not say, dates are absolute.
  • skills/ — the four things it does:
    • meeting-record — notes or a transcript into a record: overview, decisions, action items, open questions, key points, next meeting.
    • action-items — the single list: what is open, by person, overdue; mark done; add or change.
    • agenda — the next agenda from open items, open questions and new topics, with owners and minutes.
    • follow-up-message — the short message to participants: decisions and who does what by when.
  • templates/ — the shape of a record and of an agenda.
  • knowledge/examples/ — a worked example: notes into a record with four action items.
  • my/team.md — your team, regular meetings, people and roles.
  • meetings/ — one file per meeting, named by date; agendas live here too.
  • actions.md — the one list of action items across all meetings.

Things you can ask

  • "What is open for Maria?" or "What do I owe?"
  • "Mark item 7 done."
  • "Prepare the agenda for Thursday's board meeting; add the budget topic."
  • "Write the follow-up to the participants."
  • "What did we decide about the budget in September?"

Tips

  • Paste notes as they are. Fragments are fine; the assistant marks what is unclear instead of guessing.
  • Say the date of the meeting if it is not in the notes. Records are named by date.
  • Tell the assistant when something is done. It never closes an item on its own.

Credits and licenses

The sections of the record and the rule "an action item is something someone agreed to do" are adapted from the patterns summarize_meeting and transcribe_minutes from Fabric by Daniel Miessler and contributors, MIT License (licenses/fabric-MIT.txt).

# Meeting notes to actionsFor anyone who runs or sits in meetings: a team lead, a project coordinator, a board member, a parents' council. After the meeting there are rough notes or a transcript, and a week later nobody remembers who promised what. This project turns your notes into a clean record in one format, keeps a single list of action items across all your meetings, prepares the next agenda from what is still open, and writes the message to participants.## How to start1. Make a copy of this project (the "Make a copy" button).2. Connect your AI to Pacpio if you have not yet.3. Ask: "Here are my notes from today's team meeting, make a record and update the action list", and paste your notes.The first time, your assistant asks three questions: which team and meetings, who takes part, and in which language to keep records. It saves the answers in `my/team.md`.## What is inside- `AGENTS.md` — how your assistant works here: an action item is something a named person agreed to do, nothing is attributed that the notes do not say, dates are absolute.- `skills/` — the four things it does:  - `meeting-record` — notes or a transcript into a record: overview, decisions, action items, open questions, key points, next meeting.  - `action-items` — the single list: what is open, by person, overdue; mark done; add or change.  - `agenda` — the next agenda from open items, open questions and new topics, with owners and minutes.  - `follow-up-message` — the short message to participants: decisions and who does what by when.- `templates/` — the shape of a record and of an agenda.- `knowledge/examples/` — a worked example: notes into a record with four action items.- `my/team.md` — your team, regular meetings, people and roles.- `meetings/` — one file per meeting, named by date; agendas live here too.- `actions.md` — the one list of action items across all meetings.## Things you can ask- "What is open for Maria?" or "What do I owe?"- "Mark item 7 done."- "Prepare the agenda for Thursday's board meeting; add the budget topic."- "Write the follow-up to the participants."- "What did we decide about the budget in September?"## Tips- Paste notes as they are. Fragments are fine; the assistant marks what is unclear instead of guessing.- Say the date of the meeting if it is not in the notes. Records are named by date.- Tell the assistant when something is done. It never closes an item on its own.## Credits and licensesThe sections of the record and the rule "an action item is something someone agreed to do" are adapted from the patterns `summarize_meeting` and `transcribe_minutes` from Fabric by Daniel Miessler and contributors, MIT License (`licenses/fabric-MIT.txt`).