---
name: meeting-notes-to-action-list
description: Turns meeting notes or a transcript into decisions, actions with owner and due date, open questions and a short message to attendees. Use after a meeting to get a clear record. Never assigns an owner who was not named.
---

# Turn meeting notes into an action list

## When to use
Use this skill when someone shares meeting notes, a transcript or a rough summary and wants to know what was decided, who does what and by when. It suits team reviews, client calls, supplier calls and project catch-ups. Do not use it for confidential HR, legal or pay discussions unless the user confirms they are working in an approved workspace.

## What to ask for
- The notes or transcript, pasted as they are.
- The attendee list with full names and job titles.
- The meeting name and the exact date.
- Who will send the follow-up, and on which channel (email, WhatsApp, Slack).
- Anything the notes cannot show, such as who can approve spending. This one is optional.

If any of the first four is missing, ask for it before starting. The meeting date is needed to turn phrases like 'by Friday' into calendar dates.

## Steps
1. Read the whole text once before writing anything.
2. Label each point as a decision, an action, an open question or plain discussion. Leave discussion out of the record.
3. List a decision only when the notes show agreement or an approval. If it depends on a condition, keep the condition in the same line. If the notes say something was approved but not by whom, keep it as a decision and add a flag asking who approved it.
4. For each action, find who said they would do it. Use that person's full name from the attendee list, in the table and in the message.
5. If the notes say 'we', 'someone' or 'the team', write 'Owner not named'. Never choose an owner because the task seems to suit their role.
6. If two attendees share a first name and the notes do not make clear which is meant, write 'Owner unclear'.
7. Give a due date only if the notes state one. Convert day names such as 'Friday' or 'tomorrow' using the meeting date and show the original wording as well. For vague timing such as 'next week' or 'soon', write 'no date agreed' and quote the wording. Otherwise write 'no date agreed'.
8. Collect open questions: unsettled topics, plus every action missing an owner or a date, each with the question that would close it.
9. Write a short message from the sender, suited to the channel, under 150 words. List decisions and actions with owner and date, and ask attendees to reply with corrections. Use only what the notes say. Do not add approvals, reasons or firm dates that the notes do not contain.
10. List flags: assumptions, names not on the attendee list, approvals with no named approver, and unclear passages.

## Output format
Use these headings in this order.

```text
Decisions
1. <decision, with any condition and who approved it if stated>

Actions
Action | Owner | Due date | Where in the notes
<verb first> | <full name or Owner not named> | <date or no date agreed> | <short quote from the notes>

Open questions
- <question>

Message to attendees
<under 150 words, ready to send>

Flags
- Assumed: <assumption>
- <name, approval or passage that needs checking>
```

## Quality check
- Every action and decision can be traced to a line in the notes. The source column quotes the notes rather than giving line numbers.
- No owner appears who was not named in the notes.
- Every due date was stated, relative day names show the calendar date, and vague timing is not turned into a deadline.
- Conditions on decisions are kept.
- Names, amounts and quantities match the notes exactly.
- The message is short, lists every action with owner and date, adds nothing beyond the notes, and invites corrections.
- Delete anything you cannot trace to a line before giving the answer.

## Watch-outs
- Do not invent actions that sound sensible but were never discussed.
- Do not turn an opinion or a suggestion into a decision.
- Transcripts often mishear names and numbers. Flag anything that looks odd instead of correcting it silently.
- Notes may hold personal data about staff or customers. Include only what the follow-up needs, and remind the user to remove the rest and to use an approved workspace.
- A person must read the draft and the message before anything is sent. Say so at the end of the answer.