Minutes Debrief

Right after a meeting ends, this gives you a structured postmortem: what decisions got made, who owns what action items, and whether you hit the goals you prepped for. It pulls your latest recording transcript, compares it to any prep file you wrote beforehand, and flags when the same decision keeps changing across multiple meetings. The real utility is in the decision evolution tracking, it surfaces when you're flip-flopping on pricing or scope so you know what's actually settled versus still in flux. Ends with a concrete next action and a nudge to run the weekly rollup. Works standalone or as part of a prep-to-debrief loop.

GitHub stars: 1.3K
last updated: Jun 11, 2026

View on GitHub

Install

$ npx -y skills add silverstein/minutes --skill minutes-debrief --agent claude-code

Installs into .claude/skills of the current project.

Files

/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

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

Run minutes get "<exact path>" --json, require exit status 0, and use only the returned transcript and frontmatter. Never reopen the list path with the host Read tool. Extract:

SKILL.md on GitHub