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.

Informations de source

Dépôt
protosphinx/sphinxstack
Dernière activité de la source
29 juillet 2026 à 13:55
Langue détectée de SKILL.md
anglais
Étoiles
3
Forks
0

Options d'installation

Le prompt qui vérifie d'abord la source est sélectionné par défaut. Vous pouvez passer à une commande directe ou télécharger une copie locale.

Vérifiez les fichiers source

Lisez SKILL.md et les fichiers associés affichés par SkillsMP avant de décider de l'installer.

Explorateur de fichiers
2 fichiers

Affichage de SKILL.md

SKILL.md
Instructions source · Aperçu en lecture seule
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
Voir sur GitHub