Meeting Minutes

meeting-minutes skill for programming & development

A skill that generates professional meeting minutes from notes or transcripts, including action items, decisions, attendees, and follow-up tracking.

What Is This?

Overview

This skill transforms raw meeting notes or transcripts into structured minutes with key decisions, action items with owners and deadlines, and follow-up tasks in a consistent template.

Who Should Use This

Perfect for project managers, executive assistants, and team leads documenting sprint meetings, board meetings, and standups.

Why Use It?

Problems It Solves

Meeting outcomes get lost without documentation. Attendees leave with different understandings of decisions. This skill produces consistent, complete minutes ensuring accountability.

Core Highlights

  • Structured Output - Consistent format with headers, attendees, and timestamps
  • Action Item Extraction - Identifies tasks with assigned owners and due dates
  • Decision Tracking - Highlights key decisions made during the meeting
  • Follow-up Lists - Generates next steps and open questions
  • Multiple Formats - Outputs in Markdown, HTML, or document format

How to Use It?

Basic Usage

Provide meeting notes or a transcript, and this skill generates formatted minutes.

Scenario 1: From Raw Notes

Give Claude your meeting notes:

**Attendees**: Sarah (PM), Mike (Dev Lead), Lisa (QA), Tom (Design)

## Discussion Summary

The team reviewed the backlog for Sprint 14. Sarah prioritized the
checkout redesign based on user feedback data showing 23% cart
abandonment at the payment step.

Mike estimated the checkout API refactor at 5 story points. Lisa
raised concerns about regression testing for payment integrations.
Tom presented two design options; the team selected Option B with
the simplified payment form.

## Decisions

1. Proceed with checkout redesign (Option B) as top priority
2. Allocate 2 days for payment integration regression testing
3. Defer the dashboard analytics feature to Sprint 15

## Action Items

- Mike: Create technical spec for checkout API by March 6
- Lisa: Prepare regression test plan for payment flows by March 7
- Tom: Deliver final checkout mockups by March 5
- Sarah: Update stakeholders on Sprint 14 scope by March 4

Scenario 2: From Transcript

Paste a raw transcript and Claude will extract structured output:

## Decisions
1. Approved Q2 budget allocation of $150K for infrastructure
2. Selected Vendor A for the monitoring contract

## Action Items
| Owner  | Task                          | Due Date  |
|--------|-------------------------------|-----------|
| Sarah  | Send vendor contract to legal | March 6   |
| Mike   | Set up staging environment    | March 10  |
| Lisa   | Complete security audit       | March 14  |

## Open Questions
- Final pricing from Vendor A pending CFO approval

Real-World Examples

Board Meeting Documentation

A startup used this skill to generate investor-ready board meeting minutes. Consistent formatting with clear decision logs and action tracking improved board governance and audit readiness.

Engineering Standup Tracking

A development team processed daily standup transcripts into structured minutes. Over 3 months, the accumulated minutes provided clear project history for quarterly reviews and retrospectives.

Advanced Tips

Template Customization

Define a template matching your organization's format with sections like risk assessments or budget impacts.

Action Item Integration

Export action items directly into Jira, Linear, or Asana with assignee, deadline, and priority fields.

When to Use It?

Use Cases

  • Sprint Planning - Document sprint goals, capacity, and committed stories
  • Board Meetings - Produce formal minutes with motions and resolutions
  • Team Standups - Track blockers, progress, and decisions across days
  • Client Meetings - Record requirements, feedback, and agreed deliverables
  • Retrospectives - Capture improvement actions and team commitments

Related Topics

When you ask Claude these questions, this skill will activate:

  • "Create meeting minutes from these notes"
  • "Format this transcript as meeting minutes"
  • "Extract action items from this meeting"
  • "Generate professional meeting documentation"

Important Notes

Requirements

  • Meeting notes, transcript, or summary as input text
  • Attendee names for proper action item assignment
  • Meeting date and topic for document headers
  • Clarity on organizational minute format preferences

Usage Recommendations

Do:

  • Include attendee names - Enable accurate action item assignment
  • Note specific dates - Add deadlines mentioned during discussion
  • Capture exact decisions - Record what was agreed, not just discussed
  • Review before sharing - Verify accuracy of extracted items

Don't:

  • Don't skip context - Include enough background for absent stakeholders
  • Don't omit dissent - Record alternative views and concerns raised
  • Don't delay distribution - Share minutes within 24 hours of meeting

Limitations

  • Accuracy depends on quality and completeness of input notes
  • Cannot capture non-verbal context or tone from text transcripts
  • Long transcripts may require summarization that loses detail
  • Automated extraction may miss implied action items