← ClaudeAtlas

meeting-decisions-loglisted

Use when turning meeting notes, minutes or recordings into cited decisions, owners, deadlines and follow-up actions.
vincentdania/agent-skills-for-real-work · ★ 0 · DevOps & Infrastructure · score 63
Install: claude install-skill vincentdania/agent-skills-for-real-work
# Meeting Decisions Log Use when a meeting has happened and the output must be decisions, owners, and deadlines — not a transcript, and not a narrative summary that nobody can act on. ## Why this matters Most project failure is not disagreement; it is unrecorded agreement. A meeting with no decision log produces the same conversation again next month. ## Workflow 1. **Separate the four content types.** From the raw notes or recording, split content into: - **Decisions** — a choice has been made. Someone with authority said yes, no, or chose between options. - **Actions** — work to be done by a named person by a date. - **Information** — status updates and context. Log only if it changes understanding. - **Open questions** — unresolved matters requiring a future decision. These are the most commonly lost item and the most valuable. Most meeting notes fail because they record information and lose decisions. 2. **Test each decision.** A decision requires: what was decided, who decided it, and what it replaces or authorises. If no one with authority made a choice, it is not a decision — it is an opinion or an open question. 3. **Test each action.** An action requires: a verb, a single named owner, a due date, and a definition of done. If any is missing, mark it incomplete and record what is needed. Actions with two owners have no owner. 4. **Attribute statements to roles.** Where the notes record who said what on a contested matter, keep the attribution. W