minutes-debrief

Featured

Post-meeting debrief — analyzes what happened, compares outcomes to your prep intentions, tracks decision evolution. Use when the user says "debrief", "what just happened in that meeting", "what did we decide", "debrief that call", "post-meeting", "what changed", or right after stopping a recording.

AI & Automation 1,609 stars 187 forks Updated today MIT

Install

View on GitHub

Quality Score: 93/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# /minutes-debrief Post-meeting analysis that reads your latest recording, compares what happened to what you planned, and surfaces decision evolution — so nothing falls through the cracks. ## How it works This is a multi-phase interactive flow. It connects to `/minutes-prep` when a prep file exists, creating a before→after loop. ### Phase 1: Find the most recent recording ```bash minutes list --limit 5 ``` Pick the most recent recording. If there are multiple from today, ask via AskUserQuestion: "You have [N] recordings today. Which one are you debriefing?" with options listing the titles. **If no recent recording exists:** Say: "I don't see any recent recordings. Did you run `minutes record` and `minutes stop`? If the recording is from a specific meeting, tell me the title or date and I'll find it." Don't proceed without a recording to debrief. ### Phase 2: Read the transcript Use `Read` on the meeting file path. Extract from the transcript and frontmatter: - **Decisions made** (from `decisions:` frontmatter or `## Decisions` section) - **Action items created** (from `action_items:` frontmatter or `## Action Items` section) - **Key discussion points** (from `## Summary` or the transcript itself) - **Attendees** (from `attendees:` frontmatter) ### Phase 2b: Check speaker attributions If the meeting has a `speaker_map:` field in frontmatter, check the confidence levels: - **All High confidence**: Speakers are confirmed — use real names throughout the debrief. - ...

Details

Author
silverstein
Repository
silverstein/minutes
Created
8 months ago
Last Updated
today
Language
Rust
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

debrief

Meeting and transcript processing — classifies meeting type, applies name corrections, extracts insights across 7 categories, generates protocols, proposes tasks with project field mapping. Checkpoint-based workflow. Supports full 8-phase flow (with GitHub reconciliation + distribution email) and quick 5-phase flow; `--all` and `--date YYYY-MM-DD` batch flags absorb the former /process-meeting. Trigger: "/debrief", "/debrief {path}", "/debrief --quick", "/debrief --all", "/debrief --date YYYY-MM-DD", "process meeting", "transcript processing", "create minutes", "process-meeting", "meeting minutes", "process transcript".

14 Updated today
bks-lab
AI & Automation Listed

interview-debriefer

Turns one interview into structured notes within 24 hours, part of the Design Thinking Pack by Polar Bear. Use this whenever the user says "run interview-debriefer", "debrief this interview", "structure my interview notes", "here's the transcript from today's call", or an interview just ended and the notes are a wall of raw text. Use it even for "I just got off a user call".

62 Updated 3 weeks ago
polar-bear-org
AI & Automation Featured

minutes-recap

Generate a daily digest of today's meetings and voice memos — key decisions, action items, and themes across all recordings. Use when the user asks "recap my day", "what happened in my meetings today", "daily summary", "what did I discuss today", "any action items from today", or wants a consolidated view of the day's conversations.

1,609 Updated today
silverstein