Meeting Notes

Capture the raw record of the meeting before structuring anything.

Record:

• Meeting title, date, and who attended
• The purpose or agenda
• What was discussed — paste notes, a transcript, or your recollection

If the record is incomplete, ask the operator for the missing pieces.

Save the raw meeting record as a task note with task_notes_add. The next
step — Extract — reads this note.

Read the task notes with task_notes_list — the note from the Capture
step contains the raw record. Work from it.

Extract clean structure. What good looks like:

• A two- or three-line summary of the meeting
• Key discussion points, condensed
• Decisions made, stated plainly
• Action items, each with an owner and a due date where known
• Open questions still unresolved

Capture only what was said — do not invent decisions or owners.

Save the structured notes as a task note with task_notes_add. Then ask
the operator to confirm the decisions and owners are right before
distributing. This is a checkpoint — once notes go out they shape what
people act on, so the AI cannot advance until you approve.

Read the task notes with task_notes_list — the note from the Extract
step contains the confirmed notes. Work from it.

Format the notes for sharing:

• Clean, scannable layout — summary, decisions, action items, open
  questions
• Action items grouped by owner so each person sees their part
• The right destination (email, doc, channel) for this team

Share the notes with the people who need them, or hand the formatted
version to the operator to post.

Save the final shared notes as a task note with task_notes_add so the
record of what was distributed stays on file.

The meeting notes are structured and distributed. Confirm the final
notes are saved as a task note, then close out the task.