---
name: meeting-to-decision-filter
description: Extracts decisions with owners, open questions, and who needs to be looped in from any meeting transcript or post-meeting voice memo. Use after executive, pastoral, staff, or project meetings to prevent silent decision collisions.
license: CC-BY-4.0
metadata:
  author: Paul Yerrick (paulyerrick.com / COKI Studio)
  version: "1.0"
  category: executive-operations
  source: https://www.paulyerrick.com/ai/
---

# The Meeting-to-Decision Filter

Turn a messy meeting transcript or a two-minute post-meeting voice memo into a crisp alignment summary containing **three things only**: decisions made, open questions, and who was not in the room who needs to be looped in.

## When to Use This Skill

- Right after an executive team, pastoral leadership, elders, board, or cross-department planning meeting.
- After a 1-on-1 or project check-in where multiple people could walk away remembering different outcomes.
- When you have a raw transcript (Zoom, Teams, Fireflies, Otter, Apple Notes) or a rough two-minute voice memo recorded right after the meeting.

## When Not to Use This Skill (Red Lines)

- **Never paste confidential pastoral care, counseling, HR discipline, payroll, donor giving records, or minors' information** into unapproved or consumer AI tools with model training enabled.
- Strip personal names and sensitive identifying details before uploading whenever a meeting touches sensitive personnel or pastoral matters.
- Never use this skill to replace direct human follow-up on a difficult relational or leadership conversation.

## Inputs Needed

Ask the user to paste or attach:

1. **Meeting transcript or post-meeting voice memo** (required)
2. **Meeting name and date** (optional, infer if present)
3. **Key stakeholders or departments not in the room** (optional, helps flag who needs to be looped in)

If the user gives a very brief note without clear owners or deadlines, extract what is explicit and clearly mark missing owners or dates as `[Owner needed]` or `[Date needed]` rather than guessing.

## Step-by-Step Instructions

1. **Read for alignment, not play-by-play.** Ignore small talk, tangents, and circular debate. Do not write a chronological recap.
2. **Identify confirmed decisions.** Only list items where the group actually landed on a direction. Separate firm decisions from tentative ideas.
3. **Attach an owner and target date to every decision.** If no owner was explicitly named in the transcript, flag it as `[Owner needed]` so leadership closes the loop before leaving the week.
4. **Capture unresolved open questions.** List every decision that was deferred, blocked, or left ambiguous, along with what information or person is needed to resolve it.
5. **Run the "Not in the Room" check.** Scan the decisions for downstream impact on other teams (communications, campus operations, worship/production, finance, HR, volunteers, elders, or external partners) and list exactly who needs a heads-up and why.
6. **Check for silent decision collisions.** If two statements in the transcript appear to contradict each other on scope, timeline, or ownership, call it out briefly in a single alert line under Open Questions.
7. **Keep it scannable.** The full output must fit comfortably in a single Slack message, Teams post, or short email that takes under 90 seconds to read.

## Output Format

Use this exact markdown structure:

```markdown
## Meeting-to-Decision Summary
**Meeting:** [Meeting Name] | **Date:** [YYYY-MM-DD]

### 1. Decisions Made
- **[Decision in plain English]**
  - Owner: [Name or Owner needed]
  - Target date: [Date or Date needed]
  - Context (1 line max): [Why this was decided, only if needed]

### 2. Open Questions (Needs Clarity)
- **[Unresolved question or potential collision]**
  - Needed to resolve: [Person, data, or next meeting]

### 3. Who Needs to Be Looped In (Before Friday)
- **[Person or Team]:** [1-sentence summary of what affects them] (Assigned to notify: [Name or Owner needed])
```

## Voice and Style Rules

- Write in plain, grounded English. No corporate jargon, no filler, no hype.
- Never invent decisions, owners, or dates that are not in the source text.
- Never use em-dashes or emojis. Use periods, commas, colons, or parentheses instead.
- Keep every bullet to one or two lines maximum.

## Quick-Start Example

**Example Input (post-meeting voice memo):**
> Just wrapped the Q3 calendar meeting with Mark, Sarah, and Devon. We decided to move the Volunteer Appreciation Night from October 18 to October 25 so it does not collide with fall break. Sarah is going to lock the venue this week. We still have not decided whether childcare will be provided on site or reimbursed, and Mark needs to get budget numbers from finance by Thursday. Also we talked about launching the new website landing page two weeks early, which probably affects the comms team and campus pastors who were not in the room.

**Example Output:**

```markdown
## Meeting-to-Decision Summary
**Meeting:** Q3 Calendar Planning | **Date:** [Date needed]

### 1. Decisions Made
- **Move Volunteer Appreciation Night from October 18 to October 25.**
  - Owner: Sarah (venue confirmation)
  - Target date: This week
  - Context: Avoids overlap with fall break.

### 2. Open Questions (Needs Clarity)
- **Will childcare be provided on site or reimbursed?**
  - Needed to resolve: Budget numbers from finance (Mark to gather by Thursday).
- **Is the two-week early launch for the new website landing page confirmed or still a proposal?**
  - Needed to resolve: Leadership sign-off before comms adjusts its schedule.

### 3. Who Needs to Be Looped In (Before Friday)
- **Communications Team:** Potential two-week shift on the new website landing page launch and updated October 25 event date. (Assigned to notify: [Owner needed])
- **Campus Pastors:** Volunteer Appreciation Night moved to October 25. (Assigned to notify: [Owner needed])
- **Finance:** Needs to provide childcare budget numbers to Mark by Thursday. (Assigned to notify: Mark)
```
