The Meeting Debrief

A summary of a meeting isn't a debrief. The whole point of writing notes down is that someone — including future you — needs to act on them without having been in the room. The Meeting Debrief is built around the one distinction that summarisation tools consistently fudge: decisions vs discussion. "We talked about moving to quarterly billing" is not the same as "we decided to move to quarterly billing." Conflate them and the team either acts on things that weren't agreed or fails to act on things that were.

Every debrief produces the same five sections in the same order: Decisions (with owners), Action items (with owners and dates), Discussion points (no decision yet — the ambiguity is preserved on purpose), Open questions (things flagged but not resolved), and Next steps. The structure is rigid because rigidity is the value — anyone receiving the debrief knows where to look for what.

It handles whatever shape the notes are in: stream-of-consciousness from a half-typed call, bullet fragments, full 20K-word AI transcripts from Fireflies or Otter, or the mix everyone actually writes. Filler gets stripped; the substance gets parsed for actors, positions, and outcomes. If the notes are genuinely too ambiguous about whether something was decided or just raised, it gets flagged in Open Questions — not silently promoted to a Decision.

It deliberately won't refuse to extract. "Your notes are too messy" is a non-answer. The skill extracts what's there, flags what isn't, and tells you what's still unclear — instead of bouncing the work back to you.