pm-meeting-debrieflisted

# PM meeting debrief The most underused PM workflow. After every meeting, most teams lose 20 to 40 percent of the value because commitments aren't captured, decisions aren't logged, and follow-ups don't happen. This skill closes that loop. Given a Granola transcript, the skill extracts commitments, surfaces decisions, drafts follow-up messages, and proposes updates to the project state files. The user approves writes; the agent never writes to `pm-state/` without confirmation. ## When to use - Right after a meeting (within an hour), when context is fresh - At end-of-day, against all of today's transcripts - As part of `pm-morning-brief`'s "yesterday's loose threads" handling Don't use when: - The meeting has no Granola transcript (the skill needs the transcript as input) - The transcript is purely social or social-only (no work content) - A debrief has already been run on the same transcript (don't duplicate) ## How to apply ### 1. Chain to `pm-context-loader` Load `you.md`, the project list, cross-project stakeholders. ### 2. Identify the transcript If the user named a specific meeting, pull that transcript. Otherwise: - Pull recent transcripts via the Granola MCP - Identify the most recent one not yet debriefed (look for absence in the relevant project's recent decisions or todos with the meeting date) - If ambiguous, ask: *"You have [N] recent transcripts. Which one — [list]?"* ### 3. Identify the project Most meetings map to a project. Determine which: - Cro