Meeti
Transform meeting transcripts into actionable, type-aware summaries.
Workflow
- Extract metadata: Meeting title, attendees, duration
- Identify meeting type: Match to one of the four types below
- Load type-specific guidance: Read the appropriate reference file
- Process transcript: Apply core principles + type-specific rules
- Output structured notes: Use the format from the reference file
Meeting Type Detection
Analyze the transcript content and title to determine type:
| Type |
Indicators |
| 1:1 |
Two participants, career/feedback discussion, manager-report dynamic |
| Standup |
Multiple brief updates, blockers mentioned, daily/recurring cadence |
| Knowledge Transfer |
One person explaining systems/processes, onboarding context, heavy Q&A |
| Team Discussion |
Multiple participants, specific topic focus (feature, incident, brainstorm) |
Load the matching reference file:
references/one-on-one.md — 1:1 meetingsreferences/standup.md — Daily standupsreferences/knowledge-transfer.md — KT sessionsreferences/team-discussion.md — All other team meetings
Core Principles (Apply to All Types)
Always Capture
- Meeting title (infer from content if not provided)
- Attendees (list all participants mentioned)
- Duration (if available, otherwise omit)
- Meeting goal (deduce from title + discussion content)
Summarization Rules
- Keep summaries short—users will read the transcript if they want full details
- Remove filler words, broken phrasing, tangents
- Write in clear, direct language
- Use bullet points sparingly; prefer concise prose
Vague But Important Statements
If a statement seems significant but lacks specifics, include it in a Notable Mentions section rather than discarding it.
Example:
"We should probably think about that thing Sarah mentioned last week..."
→ Add to Notable Mentions: "Reference to previous discussion with Sarah—topic unclear, may need follow-up"
Action Items (Required)
Always document action items in this format:
| Action |
Owner |
Due Date |
| [Task description] |
[Name] |
[Date or TBD] |
Rules:
- Never omit an action item because details are missing
- Use "TBD" for unknown owners or dates
- Include implicit commitments ("I'll send that over" → action item)
Risks, Concerns, and Open Questions
Always capture in dedicated sections:
- Concerns Raised: Worries, objections, hesitations expressed
- Risks Identified: Potential problems, dependencies, blockers
- Open Questions: Unresolved questions needing answers
Meeting Improvement Tips
When applicable, end with 1-2 concrete suggestions for running better meetings of this type. Only include if genuinely useful—skip for well-run meetings.
Output Structure
Use this base structure, then add type-specific sections from reference files:
# [Meeting Title]
**Attendees:** [Names]
**Duration:** [Time] (if known)
**Meeting Type:** [Type]
**Goal:** [Inferred goal]
## Summary
[2-4 sentences capturing the essence]
## Key Discussion Points
[Organized by topic, not chronologically]
## Decisions Made
[Bulleted list of decisions]
## Action Items
| Action | Owner | Due Date |
|--------|-------|----------|
| ... | ... | ... |
## Concerns & Risks
[If any were raised]
## Open Questions
[If any remain unresolved]
## Notable Mentions
[Vague but potentially important items]
[Type-specific sections from reference file]
## Meeting Improvement Tips
[Optional, only if warranted]
1---2name: meeti3description: Formats and summarizes meeting transcripts into clear, concise, actionable notes. Use when processing meeting transcripts, notes, or recordings for any meeting type including 1:1s, standups, team discussions, knowledge transfer sessions, or general meetings. Transforms raw transcripts into structured summaries with action items, decisions, and follow-ups.4---56# Meeti78Transform meeting transcripts into actionable, type-aware summaries.910## Workflow11121. **Extract metadata**: Meeting title, attendees, duration132. **Identify meeting type**: Match to one of the four types below143. **Load type-specific guidance**: Read the appropriate reference file154. **Process transcript**: Apply core principles + type-specific rules165. **Output structured notes**: Use the format from the reference file1718## Meeting Type Detection1920Analyze the transcript content and title to determine type:2122| Type | Indicators |23|------|------------|24| **1:1** | Two participants, career/feedback discussion, manager-report dynamic |25| **Standup** | Multiple brief updates, blockers mentioned, daily/recurring cadence |26| **Knowledge Transfer** | One person explaining systems/processes, onboarding context, heavy Q&A |27| **Team Discussion** | Multiple participants, specific topic focus (feature, incident, brainstorm) |2829Load the matching reference file:30- `references/one-on-one.md` — 1:1 meetings31- `references/standup.md` — Daily standups32- `references/knowledge-transfer.md` — KT sessions33- `references/team-discussion.md` — All other team meetings3435## Core Principles (Apply to All Types)3637### Always Capture38- **Meeting title** (infer from content if not provided)39- **Attendees** (list all participants mentioned)40- **Duration** (if available, otherwise omit)41- **Meeting goal** (deduce from title + discussion content)4243### Summarization Rules44- Keep summaries short—users will read the transcript if they want full details45- Remove filler words, broken phrasing, tangents46- Write in clear, direct language47- Use bullet points sparingly; prefer concise prose4849### Vague But Important Statements50If a statement seems significant but lacks specifics, include it in a **Notable Mentions** section rather than discarding it.5152Example:53> "We should probably think about that thing Sarah mentioned last week..."5455→ Add to Notable Mentions: "Reference to previous discussion with Sarah—topic unclear, may need follow-up"5657### Action Items (Required)58Always document action items in this format:5960| Action | Owner | Due Date |61|--------|-------|----------|62| [Task description] | [Name] | [Date or TBD] |6364**Rules:**65- Never omit an action item because details are missing66- Use "TBD" for unknown owners or dates67- Include implicit commitments ("I'll send that over" → action item)6869### Risks, Concerns, and Open Questions70Always capture in dedicated sections:71- **Concerns Raised**: Worries, objections, hesitations expressed72- **Risks Identified**: Potential problems, dependencies, blockers73- **Open Questions**: Unresolved questions needing answers7475### Meeting Improvement Tips76When applicable, end with 1-2 concrete suggestions for running better meetings of this type. Only include if genuinely useful—skip for well-run meetings.7778## Output Structure7980Use this base structure, then add type-specific sections from reference files:8182```83# [Meeting Title]8485**Attendees:** [Names]86**Duration:** [Time] (if known)87**Meeting Type:** [Type]88**Goal:** [Inferred goal]8990## Summary91[2-4 sentences capturing the essence]9293## Key Discussion Points94[Organized by topic, not chronologically]9596## Decisions Made97[Bulleted list of decisions]9899## Action Items100| Action | Owner | Due Date |101|--------|-------|----------|102| ... | ... | ... |103104## Concerns & Risks105[If any were raised]106107## Open Questions108[If any remain unresolved]109110## Notable Mentions111[Vague but potentially important items]112113[Type-specific sections from reference file]114115## Meeting Improvement Tips116[Optional, only if warranted]117```
KeerthiNingegowda