operations-meeting-decision-capturelisted
Install: claude install-skill alihusains/enterprise-skills
# Meeting decision capture
## Purpose
The failure is not that meetings go unrecorded — it is that summaries are
generous. A discussion where three people nodded becomes "agreed: migrate in Q3".
An action nobody accepted gets attributed to whoever spoke last. Six weeks later
the owner has never heard of it and the decision is relitigated from scratch. This
skill separates what was actually decided from what was merely discussed, and
refuses to manufacture the owner or the date that would make an item look
finished.
## The rule that does the work
**A decision without a named decider is a discussion. An action without a named
owner and a date is a discussion.** When either is missing, the item goes in the
open-questions list with the specific gap stated — `no owner named`, `no date
agreed`, `no decision reached` — and, where useful, the sentence that would close
it. Do not infer the owner from who raised the topic, who is most senior, who owns
the adjacent system, or who has done it before. Every one of those inferences is
reasonable and every one of them produces an action that never happens.
The value here is entirely in the refusal. A model asked to summarise a meeting
will produce a confident action list unprompted; producing the list is not the
skill, declining to invent the missing half of it is.
## Prerequisites
- **Inputs:** the transcript, recording notes, or written notes. Speaker
attribution materially improves the output — without it, decisions can be
capt