Meeting-Minutes

# Meeting Minutes Skill — Short Internal Meetings

Purpose / Overview

This Skill produces high-quality, consistent meeting minutes for internal meetings that are 60 minutes or shorter. Output is designed to be clear, actionable, and easy to convert into task trackers (e.g., GitHub Issues, Jira). The generated minutes prioritize decisions and action items so teams can move quickly from discussion to execution.

When to Use

Use this skill when:

- Internal syncs, standups, design reviews, triage, planning or ad-hoc meetings with short duration

- Situations that require a concise record of decisions, assigned action items, and follow-ups

- Creating a standardized minutes document from a live meeting, transcript, recording, or notes

---

Operational Workflow

Phase 1: Intake (before drafting)

- Obtain meeting metadata: title, date, start/end time (or duration), organizer, and intended audience.

- Confirm available inputs: agenda, slides, recording, transcript, or raw notes.

- If key details are missing, ask up to 3 clarifying questions before producing minutes (see "Discovery" below).

Phase 2: Capture (during / immediately after meeting)

- Record attendees and absentees.

- Capture brief notes per agenda item with time markers if available.

- Record explicit decisions, rationale summary (1–2 sentences), and action items (owner + due date).

Phase 3: Drafting

- Generate minutes following the **Strict Minutes Schema** (below).

- Ensure every action item includes owner, due date (or timeframe), and acceptance criteria when applicable.

- Mark unresolved issues or items requiring follow-up in the Parking Lot.

Phase 4: Review & Publish

- If possible, send draft to meeting organizer or a designated reviewer for quick verification (within 24 hours).

- Publish final minutes to the agreed channel (shared drive, repo, ticket, or email) and optionally create tasks in the team's tracker.

---

Discovery (required clarifying questions)

Before generating minutes, the agent **MUST** ask up to three clarifying questions if any of these are missing:

- What is the meeting title, date, start time (or duration), and organizer?

- Is there an agenda or transcript/recording to reference? If yes, please provide.

- Who should be assigned as the reviewer or approver for the minutes?

If the user responds "no transcript" or "no agenda," proceed but mark source material as "ad-hoc notes" and flag potential gaps.

---

Strict Minutes Schema (Output Structure)

You **MUST** produce meeting minutes following this exact structure. If information is unavailable, use `TBD` or `Unknown` and explain how to obtain it.

1. Metadata

- **Title**:

- **Date (YYYY-MM-DD)**:

- **Start Time (UTC)**:

- **End Time (UTC) or Duration**:

- **Organizer**:

- **Location / Virtual Link**:

- **Minutes Author** (agent or person):

- **Distribution List** (who receives the minutes):

2. Attendance

- **Present**: [list of names + roles]

- **Regrets / Absent**: [list]

- **Notetaker / Recorder**: [name or "agent"]

3. Agenda

Bullet list of agenda items, in order:

- Item 1: short title

- Item 2: short title

- ...

4. Summary

A concise one-paragraph summary (1–3 sentences) of the meeting's objective and high-level outcome.

5. Decisions Made

Each as a separate bullet:

- **Decision 1**: statement of decision.

- Who decided / approved: [name(s) or group]

- Rationale (1–2 sentences): brief reason.

- Effective date (if applicable): YYYY-MM-DD

- **Decision 2**: ...

6. Action Items

Table-style bullets; **must include owner and due date**:

- **[ID] Action**: short description

- **Owner**: Name (team)

- **Due**: YYYY-MM-DD or "ASAP" / timeframe

- **Acceptance Criteria**: (what completes this action)

- **Linked artifacts / tickets**: (optional URL or ticket id)

**Example:**

- [A1] Draft deployment runbook for feature X

- Owner: Alex (Engineering)

- Due: 2026-02-05

- Acceptance Criteria: runbook includes ste