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.

Quellinformationen

Repository
protosphinx/sphinxstack
Letzte Quellaktivität
29. Juli 2026 um 13:55
Erkannte Sprache von SKILL.md
Englisch
Sterne
3
Forks
0

Installationsoptionen

Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.

Quelldateien prüfen

Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.

Datei-Explorer
2 Dateien

SKILL.md wird angezeigt

SKILL.md
Quellanweisungen · Schreibgeschützte Vorschau
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
Auf GitHub ansehen