meeting-driver
Skill0 starsChanged 6 months agoMITView on GitHub
Structures meetings with agendas, time-boxes, action items, and follow-up tracking. Use when planning, running, or writing up a meeting.
In this repository13 other files it gives its agents.
- clean-commitSkill
- context-budgetSkill
- craft-principlesSkill
- debug-circuitSkill
- memory-curatorSkill
- output-guardSkill
- plan-firstSkill
- pm-docsSkill
- ship-cycleSkill
- simplify-codeSkill
- sprint-flowSkill
- task-resumeSkill
- verify-buildSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
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 14
Every meeting produces decisions, action items, and documentation.
- Distinctive: line 20
Use when: a specific decision needs to be made.
- Distinctive: line 50
Use when: updating stakeholders on progress.
- Distinctive: line 73
Use when: generating ideas or exploring a problem space.
- Distinctive: line 109
Start on time. End on time.
- Distinctive: line 111
Every action item has an owner and a due date.
- Distinctive: line 112
If a discussion goes off-track, park it: "Great point — let's capture that as a follow-up."
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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 Driver
Every meeting produces decisions, action items, and documentation. Or it shouldn't be a meeting.
Meeting Types
Decision Meeting
Use when: a specific decision needs to be made.
# Decision Meeting: [Topic]
**Date:** [date]
**Attendees:** [list]
**Time-box:** 30 minutes
## Context (5 min)
[Brief background — what decision needs to be made and why now]
## Options (10 min)
1. [Option A] — description
2. [Option B] — description
3. [Option C] — description
## Discussion (10 min)
[Capture key points, concerns, and trade-offs raised]
## Decision (5 min)
**Decided:** [which option]
**Rationale:** [why]
**Dissent:** [any disagreements noted for the record]
## Action Items
- [ ] [Action] — @owner — due [date]Status Sync
Use when: updating stakeholders on progress.
# Status Sync: [Project/Sprint]
**Date:** [date]
**Time-box:** 15 minutes
## Progress Since Last Sync
- Completed: [list]
- In progress: [list]
## Blockers
- [Blocker] — needs [what] from [whom]
## Next Steps
- [What's coming this week]
## Questions/Decisions Needed
- [Any decisions that need stakeholder input]Brainstorm
Use when: generating ideas or exploring a problem space.
# Brainstorm: [Topic]
**Date:** [date]
**Time-box:** 25 minutes
## Problem Statement (5 min)
[What are we trying to solve?]
## Ideas (15 min)
[No critiquing during this phase — capture everything]
1. [Idea]
2. [Idea]
...
## Prioritize (5 min)
**Top 3 to explore further:**
1. [Idea] — why
2. [Idea] — why
3. [Idea] — why
## Next Steps
- [ ] [Who does what to advance the top ideas]Facilitation Rules
Before the Meeting
- Require an agenda. No agenda, no meeting.
- Set a time-box. Default: 30 minutes. Maximum: 60 minutes.
- Define the desired outcome: decision, alignment, ideas, or status update.
During the Meeting
- Start on time. End on time.
- Capture action items in real-time, not after.
- Every action item has an owner and a due date.
- If a discussion goes off-track, park it: "Great point — let's capture that as a follow-up."
After the Meeting
- Send notes within 1 hour (generate them immediately from the conversation).
- Action items go into the project's task tracking, not just the notes.
- Schedule follow-ups for decisions that need revisiting.
When to Use This Skill
- User says "let's have a meeting" or "let's discuss"
- User needs to prepare for an upcoming meeting
- User wants to document a decision or discussion that just happened
- User asks to "facilitate" or "run" a session on a topic
Structure the conversation using the appropriate template above. Guide the user through each section with time awareness.
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.

