meeting-to-actions
Purpose
Turn meeting content into a compact action record without making the user reread the whole transcript.
Use For
- Zoom transcripts
- Meeting notes
- Slack threads
- Email chains
- Doc comment threads
- Ticket discussions
- Post-meeting cleanup
- Preparing follow-up messages or ticket updates
Inputs
- Zoom transcript
- Notes
- Agenda
- Related ticket or doc context when useful
- A
reduce-to-facts ledger or conversation-state record
Guardrails
- Read before write.
- Do not send follow-ups or update tickets unless explicitly asked.
- Separate decisions made from open decisions.
- Name owners and dates only when the source supports them.
- Surface missing owners, due dates, and unclear blockers.
- Do not dump raw transcript content by default.
Portable Output Contract
- Use only the useful subset of source-backed facts, assumptions, source gaps,
stakeholder sensitivities, potential misreads, and the suggested next action.
- Use the smallest useful output.
- Label assumptions and preserve source gaps, source anchors, and confidence labels.
- When consuming upstream state, do not promote an assumption, inference, open
question, proposed action, or stakeholder position into a fact, decision,
commitment, owner, or deadline without new source support.
- Keep unresolved approvals, owners, timing, and blockers explicit in the action record.
- Do not send, publish, update tickets, create events, or mutate systems unless explicitly asked.
Output
- Decisions made
- Open decisions
- Action items with owner and due date
- Blockers
- Follow-up drafts
- Tickets/docs to update if applicable
- Source gaps
If the user wants a reusable record, use the optional CONVERSATION_STATE.md
template from this pack when it is available.
Success Standard
The user should leave the meeting with an action record they can send or use immediately.
1---2name: meeting-to-actions3description: Turn meeting notes or transcripts into decisions, action items, owners, dates, blockers, and follow-ups.4---56# meeting-to-actions78## Purpose910Turn meeting content into a compact action record without making the user reread the whole transcript.1112## Use For1314- Zoom transcripts15- Meeting notes16- Slack threads17- Email chains18- Doc comment threads19- Ticket discussions20- Post-meeting cleanup21- Preparing follow-up messages or ticket updates2223## Inputs2425- Zoom transcript26- Notes27- Agenda28- Related ticket or doc context when useful29- A `reduce-to-facts` ledger or conversation-state record3031## Guardrails3233- Read before write.34- Do not send follow-ups or update tickets unless explicitly asked.35- Separate decisions made from open decisions.36- Name owners and dates only when the source supports them.37- Surface missing owners, due dates, and unclear blockers.38- Do not dump raw transcript content by default.3940## Portable Output Contract4142- Use only the useful subset of source-backed facts, assumptions, source gaps,43 stakeholder sensitivities, potential misreads, and the suggested next action.44- Use the smallest useful output.45- Label assumptions and preserve source gaps, source anchors, and confidence labels.46- When consuming upstream state, do not promote an assumption, inference, open47 question, proposed action, or stakeholder position into a fact, decision,48 commitment, owner, or deadline without new source support.49- Keep unresolved approvals, owners, timing, and blockers explicit in the action record.50- Do not send, publish, update tickets, create events, or mutate systems unless explicitly asked.5152## Output5354- Decisions made55- Open decisions56- Action items with owner and due date57- Blockers58- Follow-up drafts59- Tickets/docs to update if applicable60- Source gaps6162If the user wants a reusable record, use the optional `CONVERSATION_STATE.md`63template from this pack when it is available.6465## Success Standard6667The user should leave the meeting with an action record they can send or use immediately.
tmusser