meeting-agendas
Skill1 starsChanged 7 months agoMITView on GitHub
Best practices for structuring meeting agendas, notes, and action items. Use when: preparing a meeting agenda, writing meeting notes, following up on action items, designing a recurring meeting structure, or improving meeting effectiveness.
In this repository42 other files it gives its agents.
- accessibility-testingSkill
- alternatives-analysisSkill
- anomaly-detectionSkill
- api-designSkill
- async-messagingSkill
- caching-strategiesSkill
- chartsSkill
- cicdSkill
- code-reviewSkill
- commsSkill
- critical-feedbackSkill
- data-analysisSkill
- databaseSkill
- data-migrationsSkill
- data-visualizationSkill
- dependency-managementSkill
- dockerSkill
- error-handlingSkill
- feature-flagsSkill
- git-workflowSkill
- goalsSkill
- ide-setupSkill
- large-changeSkill
- logging-metricsSkill
- markdown-docsSkill
- mcp-serverSkill
- okrsSkill
- presentationsSkill
- product-managementSkill
- prompt-writingSkill
- pythonSkill
- reclassificationSkill
- release-managementSkill
- retrospectivesSkill
- roadmap-planningSkill
- securitySkill
- stakeholder-commsSkill
- statisticsSkill
- status-updatesSkill
- testingSkill
- ticket-writingSkill
- typescriptSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 28
Every meeting agenda should answer three questions before the meeting starts:
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Meeting Agendas and Notes
When to Use
- Preparing an agenda for an upcoming meeting
- Writing meeting notes during or after a meeting
- Following up on action items from a previous meeting
- Designing the structure for a recurring meeting
- Improving meeting effectiveness and reducing wasted time
Agenda Structure
Every meeting agenda should answer three questions before the meeting starts:
- What are we deciding? — specific decisions to be made
- What are we reviewing? — information to share or discuss
- What do we need from attendees? — any pre-reads or preparation
Template
# [Meeting Name] — [Date]
**Duration:** 30 min
**Attendees:** [names]
**Pre-read:** [link to document, if any]
## Agenda
1. **[Topic]** (X min) — [owner]
- Context: [one sentence]
- Goal: [decision / review / brainstorm]
2. **[Topic]** (X min) — [owner]
- Context: [one sentence]
- Goal: [decision / review / brainstorm]
3. **Action items review** (5 min)
- Review open items from last meeting
## Parking Lot
Items raised but deferred to a future meeting.Rules
- Time-box every item — meetings expand to fill available time
- Assign an owner to each topic — someone drives the discussion
- State the goal — is this a decision, a review, or a brainstorm?
- Send the agenda 24 hours before — no surprises, time to prepare
- Limit to 3-5 items — more than that means the meeting is too long
Meeting Notes
Template
# [Meeting Name] — [Date]
**Attendees:** [names]
## Decisions
- [Decision 1]: [what was decided and why]
- [Decision 2]: [what was decided and why]
## Discussion Summary
- [Topic]: [key points raised, dissenting views if any]
## Action Items
| Action | Owner | Due |
|--------|-------|-----|
| [what] | [who] | [when] |Rules
- Capture decisions, not discussion — notes should be scannable
- Every action item has an owner and a due date — otherwise it won't happen
- Send notes within 24 hours — while context is fresh
- Link to artifacts — if a doc was discussed, link to it
Recurring Meetings
For recurring meetings (standups, retros, 1:1s), define a standing structure:
| Meeting | Frequency | Standard Agenda |
| Standup | Daily | Blockers, priorities today, announcements |
| Sprint retro | Biweekly | What went well, what to improve, action items |
| 1:1 | Weekly | Career updates, blockers, feedback |
| Team sync | Weekly | Project updates, decisions needed, announcements |
Anti-patterns
| Pattern | Problem |
| No agenda | Meeting meanders, no clear outcome |
| Too many attendees | Decision-making stalls |
| No action items | Discussion without follow-through |
| Meeting could be an async message | Wastes synchronous time |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

