Skip to content

borghei/Claude-Skills / project-management/execution/summarize-meeting

summarize-meeting

Verified

Turns meeting notes or transcripts into a summary of decisions, owned and dated action items, and open questions. Use when writing up a meeting, a recap email or a decision log; for patterns across a series use meeting-analyzer.

assets/meeting_summary_template.md

View on GitHub
# Meeting Summary

## Metadata

| Field | Value |
|-------|-------|
| **Date** | [YYYY-MM-DD] |
| **Time** | [HH:MM] - [HH:MM] [TZ] |
| **Participants** | [Name, Role]; [Name, Role]; [Name, Role] |
| **Topic** | [One-line meeting purpose] |
| **Location** | [Room / Video link / Async] |

## Summary

- [Key discussion point 1 -- what was discussed and why it matters]
- [Key discussion point 2]
- [Key discussion point 3]
- [Key discussion point 4, if applicable]

## Action Items

| Due Date | Owner | Action |
|----------|-------|--------|
| [YYYY-MM-DD] | [Single owner name] | [Specific, verifiable action with active verb] |
| [YYYY-MM-DD] | [Single owner name] | [Specific, verifiable action with active verb] |
| [YYYY-MM-DD] | [Single owner name] | [Specific, verifiable action with active verb] |

## Decisions Made

1. **[Decision statement]** -- [Brief rationale or context]. Decided by [who].
2. **[Decision statement]** -- [Brief rationale or context]. Decided by [who].

## Open Questions

1. [Unresolved question]? ([Who is expected to answer, by when])
2. [Unresolved question]? ([Who is expected to answer, by when])

---

**File name:** `Meeting-Summary-[YYYY-MM-DD]-[topic-slug].md`
**Distributed to:** [List of recipients]
**Next meeting:** [Date and time, if recurring]

---

# Follow-Up Email Template

**Subject:** Meeting Summary: [Topic] -- [Date]

Hi team,

Attached is the summary from today's [topic] meeting. Key highlights:

- **Decisions:** [1-2 sentence summary of the most important decisions]
- **Actions:** [Number] action items assigned -- see the summary for details and due dates.
- **Open:** [Number] questions remain open -- owners noted in the summary.

Please review and flag any corrections by [deadline].

Thanks,
[Your name]

---

# Decision Log Template

Use this format to maintain a running log of decisions across meetings.

| Date | Meeting | Decision | Rationale | Decided By | Status |
|------|---------|----------|-----------|------------|--------|
| [YYYY-MM-DD] | [Meeting name] | [Decision] | [Why] | [Who] | Active / Superseded / Reversed |
add-product-e2e-evalpaperclipai/paperclipAdd or extend a Paperclip full-stack runner E2E workflow, fixture, matcher, or report evidence path for local or Daytona execution.Stars: 115kUpdated Claude CodeCodexVerifiedInstall
add-runner-evalpaperclipai/paperclipAdd or extend a Paperclip Runner protocol evaluation definition, roster, assertion, or report fixture with provenance and narrow validation.Stars: 115kUpdated Claude CodeCodexVerifiedInstall
diagnose-why-work-stoppedpaperclipai/paperclipCompatibility entry point for failed, stalled, looping, or over-recovered Paperclip work. Use fix-failed-paperclip-run for the full diagnosis, regression, repair, real verification, and green-PR workflow; honor an explicitly requested diagnosis-only scope.Stars: 115kUpdated Claude CodeCodexVerifiedInstall
fix-failed-paperclip-runpaperclipai/paperclipDiagnose and fix failed, stuck, slow, or incorrectly blocked Paperclip tasks and runs. Use with a task/run URL or failure report to trace the root cause, prove a regression red then green, check second-order effects, verify the real workflow, and deliver a PR with passing checks.Stars: 115kUpdated Claude CodeCodexVerifiedInstall