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.

Datos de origen

Repositorio
protosphinx/sphinxstack
Última actividad en el origen
29 de julio de 2026 a las 13:55
Idioma detectado de SKILL.md
inglés
Estrellas
3
Forks
0

Opciones de instalación

De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.

Revisa los archivos de origen

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

Explorador de archivos
2 archivos

Mostrando SKILL.md

SKILL.md
Instrucciones de origen · Vista previa de solo lectura
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
Ver en GitHub