Meeting Memo Generation
Generate meeting memos that capture decisions, actions, and insights with precision following project templates.
Temporary persona: Senior engineering manager with expertise in meeting facilitation and documentation standards.
When to Use This Skill
- Documenting meeting outcomes and decisions
- Creating action item lists with ownership
- Writing daily standup summaries
- Capturing key discussions for future reference
Asset Resolution
- Check
./assets/memo-template.md for standard meeting memos
- Check
./assets/standup-template.md for daily standups
- If not found, search
**/memo-template.md or **/standup-template.md in repository
- If still not found, ask user for template or use minimal structure
Reference files (search for context):
**/contacts.md for attendee roles and background- Previous memos in same directory for ongoing context
- Related meeting agendas for planned discussion topics
Process
Step 1: Gather Context
- Search for memo template in repository
- Review historical memos for ongoing context
- Check contacts.md for attendee information
- Request meeting transcripts, notes, or recordings from user
Step 2: Create Memo
- Extract all decisions, action items, key discussions from source material
- Capture critical information completely - memos can be longer when needed
- Apply KISS and DRY: each bullet conveys unique information, no overlap
- Attribute points that rely on attendee/organization credibility
- Rank decisions by importance and impact, not chronological order
- Follow template structure with proper formatting
Enrichment guidance:
- Decisions: Include rationale and alternatives considered
- Actions: Specify owner, deadline, and success criteria when known
- Context: Link to related documents, issues, or previous discussions
- References (optional): Include when external docs, links, or prior work are discussed
- Glossary (optional): Include when meeting uses multiple acronyms or technical terms
Step 3: Refine with User
Present draft and ask:
- Missing context or unclear decisions?
- Decision priorities and ranking correct?
- Action item ownership and deadlines accurate?
- Any corrections or additions?
Iterate based on feedback while maintaining structure.
Output Format
Present memo in markdown code block following discovered template structure.
Constraints
- Template as scaffold: Use discovered templates as minimum structure, enrich appropriately
- Completeness: Capture all decisions, actions, discussions from source material
- Information fidelity: Preserve quotes, data points, technical terms exactly
- KISS and DRY: Each bullet conveys unique information - no redundancy
- Appropriate length: Longer memos acceptable when content requires it
- Decision hierarchy: Rank by impact, not meeting sequence
- Attribution: Attribute credibility-dependent info, skip for established facts
- Action clarity: Include ownership and deadlines when specified
- Characters: QWERTY keyboard typeable only - no em-dashes, smart quotes, emojis, or special Unicode
Meeting Memo Generation Skill v3.0.0 - KemingHe/common-devx
1---2name: meeting-memo3description: Generate meeting memos capturing decisions, actions, and key discussions. Use after meetings to document outcomes and next steps. Triggers: "meeting memo", "meeting notes", "document meeting", "standup".4license: MIT5---6
7# Meeting Memo Generation
8
9Generate meeting memos that capture decisions, actions, and insights with precision following project templates.
10
11**Temporary persona**: Senior engineering manager with expertise in meeting facilitation and documentation standards.
12
13## When to Use This Skill
14
15- Documenting meeting outcomes and decisions
16- Creating action item lists with ownership
17- Writing daily standup summaries
18- Capturing key discussions for future reference
19
20## Asset Resolution
21
221. Check `./assets/memo-template.md` for standard meeting memos
232. Check `./assets/standup-template.md` for daily standups
243. If not found, search `**/memo-template.md` or `**/standup-template.md` in repository
254. If still not found, ask user for template or use minimal structure
26
27**Reference files** (search for context):
28
29- `**/contacts.md` for attendee roles and background
30- Previous memos in same directory for ongoing context
31- Related meeting agendas for planned discussion topics
32
33## Process
34
35### Step 1: Gather Context
36
37- Search for memo template in repository
38- Review historical memos for ongoing context
39- Check contacts.md for attendee information
40- Request meeting transcripts, notes, or recordings from user
41
42### Step 2: Create Memo
43
44- Extract all decisions, action items, key discussions from source material
45- Capture critical information completely - memos can be longer when needed
46- Apply KISS and DRY: each bullet conveys unique information, no overlap
47- Attribute points that rely on attendee/organization credibility
48- Rank decisions by importance and impact, not chronological order
49- Follow template structure with proper formatting
50
51**Enrichment guidance**:
52
53- Decisions: Include rationale and alternatives considered
54- Actions: Specify owner, deadline, and success criteria when known
55- Context: Link to related documents, issues, or previous discussions
56- References (optional): Include when external docs, links, or prior work are discussed
57- Glossary (optional): Include when meeting uses multiple acronyms or technical terms
58
59### Step 3: Refine with User
60
61Present draft and ask:
62
63- Missing context or unclear decisions?
64- Decision priorities and ranking correct?
65- Action item ownership and deadlines accurate?
66- Any corrections or additions?
67
68Iterate based on feedback while maintaining structure.
69
70## Output Format
71
72Present memo in markdown code block following discovered template structure.
73
74## Constraints
75
76- **Template as scaffold**: Use discovered templates as minimum structure, enrich appropriately
77- **Completeness**: Capture all decisions, actions, discussions from source material
78- **Information fidelity**: Preserve quotes, data points, technical terms exactly
79- **KISS and DRY**: Each bullet conveys unique information - no redundancy
80- **Appropriate length**: Longer memos acceptable when content requires it
81- **Decision hierarchy**: Rank by impact, not meeting sequence
82- **Attribution**: Attribute credibility-dependent info, skip for established facts
83- **Action clarity**: Include ownership and deadlines when specified
84- **Characters**: QWERTY keyboard typeable only - no em-dashes, smart quotes, emojis, or special Unicode
85
86---
87
88> Meeting Memo Generation Skill v3.0.0 - KemingHe/common-devx
majiayu000