Skip to main content

write-meeting-notes

Capture a meeting's evidence, decisions, dissent, actions, owners, and unresolved questions. Use when participants need an accurate operating record rather than a transcript.

Source facts

Repository
protosphinx/sphinxstack
Last source activity
July 29, 2026 at 13:55
Detected SKILL.md language
English
Stars
3
Forks
0

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer
2 files

Showing SKILL.md

SKILL.md
Source instructions · Read-only preview
name
write-meeting-notes
category
write
description
Capture a meeting's evidence, decisions, dissent, actions, owners, and unresolved questions. Use when participants need an accurate operating record rather than a transcript.
# write-meeting-notes Record what changed because the meeting happened. Distinguish discussion from decisions and proposed actions from accepted commitments. ## Procedure 1. Confirm audience, note owner, privacy level, retention, and whether recording or attribution is permitted. 2. Copy the meeting purpose, date, participants, agenda, and pre-read links. 3. Capture material evidence, assumptions, constraints, and corrections with precise artifact locators. 4. Record each decision with scope, owner, rationale, alternatives, dissent, effective date, and revisit trigger. 5. List actions with one owner, due date, acceptance evidence, and dependency. 6. Separate open questions, parked topics, and risks from completed conclusions. 7. Mark statements needing verification rather than converting them into facts. 8. Circulate a concise draft promptly and give participants a bounded correction window. 9. Reconcile corrections, publish the final record, and update the relevant system of record. ## Failure plan - Do not create a verbatim or attributed record when participants were not informed. - Never store health, identity, complaint, personnel, security, or legal detail in an unrestricted document. - If participants dispute a decision, preserve the disagreement and ask the authorized owner to resolve it. - Do not infer commitment from silence. ## Done - Decisions, actions, owners, dates, evidence, and open questions are clearly separated - Factual corrections are reconciled and unresolved disputes remain visible - Final notes are saved in the authorized location and linked from follow-up work
View on GitHub