meeting-notes
turn a raw conversation into decisions, owners and dates
Decisions at the top, then actions with a name and a date, then what was left open and who closes it. Run it after any conversation that decided something, or failed to.
structure generate skill meeting-notesSkill — meeting-notes
Invoke in any agent conversation with /meeting-notes. The steps below are a starting opinion, and
they are what runs — edit them until they describe the notes this company would still find useful in
a month.
When to use. After any conversation that decided something, and after any conversation that failed to.
Steps.
- Decisions first, at the top. One line each, with who made it and the date.
- Then actions: a person, a thing, and a date. An action with no name attached is a wish.
- Then what the room did not settle, and who has to close it.
- Then the context worth keeping — briefly. This is not a transcript, and nobody rereads one.
- Mark anything you inferred as inferred. If you cannot tell whether it was decided, it goes on the open list.
- Spell people as the roster spells them, so the notes address real actors.
- File it in
memory/— notes record, they do not steer. Anything that must steer becomes a proposal to the document it changes.
---
type: skill
name: meeting-notes
description: turn a raw conversation into decisions, owners and dates
standing: draft
owner: "{{owner}}"
updated: "{{date}}"
---
# Skill — meeting-notes
_Invoke in any agent conversation with `/meeting-notes`. The steps below are a starting opinion, and
they are what runs — edit them until they describe the notes this company would still find useful in
a month._
**When to use.** After any conversation that decided something, and after any conversation that
failed to.
**Steps.**
1. Decisions first, at the top. One line each, with who made it and the date.
2. Then actions: a person, a thing, and a date. An action with no name attached is a wish.
3. Then what the room did not settle, and who has to close it.
4. Then the context worth keeping — briefly. This is not a transcript, and nobody rereads one.
5. Mark anything you inferred as inferred. If you cannot tell whether it was decided, it goes on the
open list.
6. Spell people as the roster spells them, so the notes address real actors.
7. File it in `memory/` — notes record, they do not steer. Anything that must steer becomes a
proposal to the document it changes.
type: skill
name: meeting-notes
about: "Decisions at the top, then actions with a name and a date, then what was left open and who closes it. Run it after any conversation that decided something, or failed to."
version: "0.1.0"