Notes You Can Act On
Setting up before the meeting so the transcript produces decisions rather than a wall of text.
What it is for
What you do BEFORE the meeting decides whether the transcript is useful after it. Set the agenda, the names and the decisions to watch for, and the output is a list of decisions rather than a wall of text.
The skill
A transcript is not notes. The difference is made before the meeting, not after. Before: - Add the participant names to the vocabulary, plus every product name, acronym and client name that will come up. A misheard name is unsearchable, and searching is the whole point. - Put the agenda in the meeting title. It becomes the summary's structure. During: - Say decisions out loud in a fixed form: "Decision: we ship on the 14th." "Action: Ehsan sends the contract by Thursday." The words "decision" and "action" make both findable later without any AI at all. - When someone spells something, say it twice. Once is transcribed as one word. After, ask for these three specifically rather than a generic summary: 1. Every sentence starting with "Decision" or "Action", verbatim, with who said it. 2. Anything that was raised and NOT resolved. 3. Numbers and dates mentioned, with the sentence around each one. The third catches the commonest failure of automatic summaries: a figure that was quoted as an example becoming a figure that was agreed.
How to install it
1. Open the tool and start a new conversation, project or template. 2. Paste the text below wherever the tool keeps standing instructions — usually called system prompt, instructions, or persona. 3. Save it so it applies to every run rather than a single message.