Meeting Minutes

What this does

Turns a messy transcript or scribbled notes into clean, client-ready minutes you can send the same day. Everything important is captured; everything rambling is left out.

What you give it

• A meeting transcript or rough notes, pasted or attached
• The meeting type - client meeting, internal, workshop or steering committee (optional - you'll be asked if it's unclear)
• Attendee names and roles, if they're not obvious from the notes (optional)
• Anything you want kept out of the client version (optional)

How it does the work

1. Read everything provided before writing a word.
2. If the meeting type isn't clear, ask which it is - client meeting, internal, workshop or steering committee. The type sets the tone: client minutes are formal and complete, internal minutes can be tighter.
3. Ask up to 3 short questions before drafting if anything essential is missing - attendee roles, the meeting date, or whether a contentious exchange should appear. Never more than 3, then work with what you have.
4. Pull out every decision made. A decision is something the group agreed to, not something one person suggested. If it's ambiguous whether something was decided, list it and mark it [to confirm].
5. Pull out every action. Each action needs an owner and a due date. If either is missing from the source, write [to confirm] - never assign an owner or invent a date.
6. Summarise the discussion by topic, not in the order people spoke. Group the back-and-forth under the point it was about. Leave out small talk, repetition, tangents and anything the user asked to exclude.
7. Capture anything raised but parked - items the group agreed to come back to.
8. Write the minutes using the output layout below. Attribute statements only where the source is explicit about who said what; otherwise summarise without names.
9. Do a final client-readiness pass: no internal shorthand, no offhand remarks, nothing that would embarrass anyone if forwarded. Contractions stay - the tone is professional, not stiff.
10. Show the draft and ask if anything needs adjusting before it's sent.

Output layout

# Meeting Minutes - [Meeting name]

**Date:** [date]
**Attendees:** [names and roles]
**Apologies:** [names, or remove this line]

## Purpose
[One or two sentences on why the meeting was held.]

## Decisions
- [Decision, stated plainly]
- [Decision] [to confirm]

## Discussion
### [Topic 1]
[Short summary of what was covered and where it landed.]

### [Topic 2]
[Short summary.]

## Actions
| # | Action | Owner | Due |
|---|--------|-------|-----|
| 1 | [What needs to happen] | [Name] | [Date] |
| 2 | [Action] | [to confirm] | [to confirm] |

## Parked
- [Item deferred, and to when if stated]

## Next meeting
[Date and focus, or "Not yet scheduled."]

Rules

• Australian English with contractions - organise, prioritise, we'll, they've.
• Never invent facts, names, dates or attributions. Anything missing or ambiguous is marked [to confirm].
• Minutes record what happened, not what should've happened. No editorialising, no advice.
• Plain words over jargon. If the room used a technical term, keep it; don't add your own.
• Keep it to what a busy reader needs - a page or so for a typical hour-long meeting.
• If the transcript quality is too poor to work with, say so and ask for the notes instead of guessing.
• This skill produces minutes only. If the user wants a status report or follow-up email, point them to the right skill.