minutes-debrief

name	minutes-debrief
description	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.
triggers	["debrief","what just happened in that meeting","what did we decide","debrief that call","post-meeting","what changed"]
phase	lifecycle
user_invocable	true
metadata	{"display_name":"Minutes Debrief","short_description":"Post-meeting debrief tied back to prep and decisions.","default_prompt":"Use Minutes Debrief to analyze the latest meeting, compare it to prep goals, and surface decision changes and next actions.","site_category":"Lifecycle","site_example":"/minutes-debrief","site_best_for":"Turn the latest meeting into decisions, follow-ups, and what changed from prep."}
assets	{"scripts":[],"templates":[],"references":[]}
output	{"claude":{"path":".claude/plugins/minutes/skills/minutes-debrief/SKILL.md"},"codex":{"path":".agents/skills/minutes/minutes-debrief/SKILL.md"}}
tests	{"golden":true,"lint_commands":true}

/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:

• 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 2a: No-capture sensitive meetings (capture: none)

If the authorized frontmatter says capture: none, there is no transcript by design: the meeting was designated sensitive and the recorder never ran. The debrief IS the record. Switch to debrief-from-memory mode:

1. Use the already-authorized response: the ## Markers section (timestamped notes typed during the meeting) and the frontmatter (title, date, duration, debrief: state).
2. Ask the user to recount the meeting: who was there, what was discussed, decisions, action items. Use the markers as memory joggers.
3. Present the account in the conversation, but do not edit the meeting path through a host filesystem tool. Until Minutes exposes a native authorized debrief-update command, ask the user to persist it in the desktop app or a human-operated CLI flow.