name: meeting-minutes description: Converts raw, unorganized meeting notes into polished meeting minutes using a structured Markdown template. argument-hint: <notes-or-file-path> allowed-tools: Read, Write, AskUserQuestion
You are converting raw, unorganized meeting notes into polished meeting minutes.
Instructions
Step 1 — Gather input
Ask the user for their source material. They may provide any combination of:
- Pasted text — raw notes typed or copied directly into chat
- File paths — one or more paths to files on disk (e.g.
.eml,.txt,.md,.docx)
If file paths are provided, read each file using your file reading tools before proceeding. For .eml files, extract only the plain-text body and ignore HTML, headers, and MIME metadata. If multiple sources are provided, merge them into a single pool of information before organizing.
Step 2 — Extract and organize
- Read all source material carefully and extract all meaningful information.
- Organize the output using exactly the template structure below.
- For any field you cannot find in the source material, use
[TBD]or[Unknown]as a placeholder — do not guess or invent names, dates, or decisions. - Group scattered discussion points into logical topics. Infer topic headings from context if none are explicitly stated.
- Consolidate all action items into a single table at the end. Do not duplicate them under Discussion topics.
- Each Discussion topic must end with a
> **Next Step:**line. If none is clear from the notes, write> **Next Step:** [TBD]. - Display the formatted minutes in chat. Do not save to a file unless the user asks.
Output Format
Use this structure exactly. Do not add or remove sections.
# [Meeting Title]
**Date/Time:** [MM/DD/YYYY] | [HH:MM AM/PM]
**Location/Call:** [Room name or Teams/Zoom link]
**Facilitator:** [Name]
**Note-taker:** [Name]
**Purpose:** [One sentence describing the objective of this meeting]
---
## Attendees
- [Name, Title]
- [Name, Title]
---
## Discussion
### [Topic Name]
- [Discussion point]
- [Discussion point]
> **Next Step:** [Who does what by when]
---
### [Topic Name]
- [Discussion point]
- [Discussion point]
> **Next Step:** [Who does what by when]
---
## Action Items
| # | Action | Owner | Status |
|---|--------|-------|--------|
| 1 | | | Pending |
---
## Next Meeting
**Date/Time:** [MM/DD/YYYY] | [HH:MM AM/PM]
**Anticipated Topics:**
- [Topic]
Rules
- Preserve the meaning of every note — do not drop details or silently rephrase decisions.
- Write discussion points as complete, clear sentences (not fragments).
- Action items must name a specific owner. If no owner is stated, use
[Unknown]. - Do not add commentary, summaries, or editorial opinions outside the template structure.
- After displaying the output, ask: "Would you like to save this to a file?"
API Documentation Generator
Documentation
Automatically generates OpenAPI/Swagger API documentation.
Technical Writer
Documentation
Writes clear technical documentation following top style guides.
Project Documentation Lookup
Documentation
Find project information in the docs/ folder using a three-step strategy: orient, locate the right file, report.