Meeting Notes

Meeting Notes turns a supplied transcript or rough notes into concise minutes that help absent readers catch up and show attendees what they owe. It looks for what was finally decided before reviewing the reasoning. The resulting document captures conclusions and stated disagreement rather than reproducing the discussion in chronological order.

The skill organizes material into decisions, action items and open questions. Decisions state what was adopted, rather than merely saying a subject was discussed. Action items identify an owner and deadline. Open questions identify what remains unresolved, what blocks progress and who owns the next step. The minutes begin with up to three lines explaining what the meeting decided, followed by those three groups.

Use it when someone pastes meeting notes or a transcript and requests minutes or a summary, or when recorded decisions and follow-up work need clearer organization. It works only with the supplied notes. It cannot join the meeting, recover audio or resolve a name that the notes never recorded.

A topic mentioned as discussed does not automatically become a decision. If the notes do not record adoption, the skill reports the topic as an open question. It records the available decisions rather than treating every discussion as consensus. Likewise, an action described vaguely as everyone's responsibility needs an explicit missing-owner marker rather than an invented assignment.

The input is the user's raw notes or transcript. The output is a conclusion-first set of minutes with affirmative decision statements, action items and unresolved questions. Missing action owners are marked [unassigned], and missing deadlines are marked [TBD]. Other missing names, dates or numbers are marked [to confirm]. None are guessed to make the document appear complete.

An affirmative decision can take this form:

### Decisions
- Adopt a cache layer for login-page performance (pilot first, not a full rollout).

Reasons are included only when stated in the notes. The skill avoids editorial judgments about proposals or participants: it can report a rejection and its recorded reason, but cannot substitute an opinion for the record.

Before output, it checks every action for an owner and deadline, every decision for an affirmative statement, and every open question for a next step. Any missing element is flagged rather than hidden. The minutes body is limited to one-third of the raw notes, so detailed discussion is deliberately condensed. If the output exceeds that limit, it is distilled again. The result remains only as complete as the material supplied, with unresolved responsibilities and timing made visible for confirmation.