From design-ops
Generates structured meeting recap from notes or transcripts, including summary, key decisions, action items with owners and deadlines, highlights, open questions, and next steps. Offers saves to Notion.
npx claudepluginhub opensesh/design-ops --plugin design-opslibrary/logistics/# /meeting-recap Post-meeting documentation workflow that generates summaries with action items, owners, and deadlines. ## Trigger User invokes `/meeting-recap` after a meeting to create structured documentation. ## Optional MCP Servers - Notion (to store the recap) - Google Calendar (to attach to the event) --- ## Workflow ### Step 1: Gather Notes Ask the user for meeting notes: "How would you like to provide the meeting notes?" - Paste them here - Share a file path - Share a recording transcript link ### Step 2: Clarify Context (if needed) If the notes are sparse, ask: - "What...
/meeting-recapGenerates topic-segmented post-meeting recap from transcripts/notes, highlights decisions, captures actions per topic inline, and provides consolidated actions view.
/meeting-notesSummarizes meeting transcripts or notes into structured Markdown notes with attendees, topics, decisions, action items, highlights, and next steps.
/devkit.write-a-minute-of-a-meetingGenerates structured meeting minutes from transcript file, with executive summary, agenda discussions, decisions, action items table, and next steps. Requires transcript-file, meeting-title, date.
/meeting-endStop the meeting Voice Memo, draft notes, and prepare follow-up email to attendees.
/summarize-transcriptSummarizes transcripts, meeting notes, or discussion threads into structured actionable documents with TL;DR, breakdowns, action items, and customizable styles via presets and guidance flags.
Share bugs, ideas, or general feedback.
Post-meeting documentation workflow that generates summaries with action items, owners, and deadlines.
User invokes /meeting-recap after a meeting to create structured documentation.
Ask the user for meeting notes:
"How would you like to provide the meeting notes?"
If the notes are sparse, ask:
Process the notes into a structured recap:
## Meeting Recap: [Title]
**Date:** [Date]
**Attendees:** [Names]
**Duration:** [If known]
### Summary
[2-3 sentence overview of what was discussed and decided]
### Key Decisions
- **[Decision 1]** - [Context if needed]
- **[Decision 2]** - [Context if needed]
### Discussion Highlights
- [Key point 1]
- [Key point 2]
- [Key point 3]
### Action Items
| Action | Owner | Due Date |
|--------|-------|----------|
| [Task 1] | [Name] | [Date] |
| [Task 2] | [Name] | [Date] |
| [Task 3] | [Name] | [Date] |
### Open Questions / Parking Lot
- [Unresolved item 1]
- [Unresolved item 2]
### Next Meeting
[Date/time if scheduled, or "TBD"]
After presenting the recap, ask:
When extracting from raw notes:
Finding Decisions:
Identifying Action Items:
Summary Quality:
User: /meeting-recap
Claude: "How would you like to provide the meeting notes?"
User:
design review call today with taylor and morgan
- looked at homepage redesign
- taylor likes the hero but wants to explore different cta colors
- morgan pointed out accessibility issues with the contrast
- need to fix contrast before next review
- decided to go with option B for the nav
- taylor will send mood board by friday
- next review tuesday
Claude generates:
## Meeting Recap: Design Review - Homepage Redesign
**Date:** [Today's date]
**Attendees:** Taylor, Morgan, [You]
### Summary
Reviewed homepage redesign progress. Approved Option B for navigation. Identified accessibility concerns with CTA contrast that need resolution before next review.
### Key Decisions
- **Navigation:** Going with Option B
- **Hero:** Approved, but exploring alternative CTA colors
### Discussion Highlights
- Taylor positive on hero design overall
- Morgan flagged contrast/accessibility issues with current CTA
- CTA color exploration needed to meet accessibility standards
### Action Items
| Action | Owner | Due Date |
|--------|-------|----------|
| Send mood board for CTA color exploration | Taylor | Friday |
| Fix CTA contrast to meet accessibility standards | [Owner TBD] | Before Tuesday |
| Schedule accessibility audit if needed | [Owner TBD] | [Date TBD] |
### Open Questions
- What WCAG level are we targeting for contrast?
- Are there brand constraints on CTA colors?
### Next Meeting
Tuesday (design review)
Version: 1.0