Skip to content

Communication · For your bots

Meeting notes to action items

Turn a meeting transcript or rough notes into decisions, owned actions with dates, and open questions, and nothing else.

In Lobstack: Skills › Library › Add

Download Lobstack

When to use it

A transcript, recording summary or page of notes arrives and somebody needs to know what was agreed and who owes what.

What your bot will do

  1. 01

    Read all of it before writing. Decisions get reversed twenty minutes later; only the final position counts.

  2. 02

    Decisions: one line each, with a short quote of the moment it was settled, so it can be checked against memory.

  3. 03

    Actions as a table: action, owner, due date, source line. An owner is a named person. "We", "the team" or "someone" is not — move those to Open questions as "needs an owner".

  4. 04

    Convert dates as said ("by Friday") into real dates from the meeting date. Where none was given, write "no date"; never invent one.

  5. 05

    Open questions: what was raised and not settled, and who could settle it.

  6. 06

    Leave out small talk, status recitals, and anything repeated from an earlier meeting unless it changed.

  7. 07

    Post it as a document. Offer to create the actions as tickets or send the summary to attendees, and wait for a yes — both are writes to other people's tools.

If the notes are too thin to name owners for most actions, say so at the top rather than guessing.

The file

meeting-notes-to-actions/SKILL.md34 lines
---name: meeting-notes-to-actionsdescription: "Turn a meeting transcript or rough notes into decisions, owned actions with dates, and open questions, and nothing else."metadata:  title: "Meeting notes to action items"  category: communication  tags: [meetings, actions]--- ## When to use this A transcript, recording summary or page of notes arrives and somebody needs toknow what was agreed and who owes what. ## How 1. Read all of it before writing. Decisions get reversed twenty minutes later;   only the final position counts.2. Decisions: one line each, with a short quote of the moment it was   settled, so it can be checked against memory.3. Actions as a table: action, owner, due date, source line. An owner is a   named person. "We", "the team" or "someone" is not -- move those to Open   questions as "needs an owner".4. Convert dates as said ("by Friday") into real dates from the meeting date.   Where none was given, write "no date"; never invent one.5. Open questions: what was raised and not settled, and who could settle it.6. Leave out small talk, status recitals, and anything repeated from an earlier   meeting unless it changed.7. Post it as a document. Offer to create the actions as tickets or send the   summary to attendees, and wait for a yes -- both are writes to other people's   tools. If the notes are too thin to name owners for most actions, say so at the toprather than guessing.

Get Lobstack.