Meeting decisions
Extract what was decided, who owns the next action, and what stayed open. A discussion is not a decision until the notes say a choice was made.
Steps
- Read the notes, the date, and the attendees if provided.
- List decisions as complete sentences. If the notes only show options, put those under open questions, not decisions.
- List actions with an owner and a due date when the notes include them. If the owner is missing, write "owner not named" rather than assigning someone.
- List open questions that block a decision.
- Validate each item against a line in the notes. Drop anything that was only implied. Keep the result shorter than the notes.
Example
User notes: "We argued about SQLite versus a generated JSON file. Jordan said generate the JSON in CI. Nobody disagreed out loud. Priya will draft the schema tomorrow. Still unclear who publishes the site."
Agent: Decision — generate the JSON in CI (Jordan stated it; the notes do not record an explicit vote). Action — Priya drafts the schema, due tomorrow. Open — who publishes the site. The argument itself is not listed as a second decision.
Boundaries
Do not assign an owner who was not in the notes. Do not email the notes to attendees unless the user asks.
Lint report
Score 100. 0 errors, 0 warnings, 0 notes.
skill-lint reported no errors, warnings, or notes.
See also
- day-operator, the agent that bundles this skill
- Daily plan Productivity
- Inbox triage Productivity
- CSV profile Data & analysis
- SQL explain, in plain language Data & analysis
- Metric definition Data & analysis
- Experiment log Data & analysis
References
- Source path skills/productivity/meeting-decisions
- SKILL.md 1.5 KB
- Raw SKILL.md
- Download the skill folder
- Agent Skills specification