agentleFS
stephenroganstephenrogan/csm-skills/skills/meeting-agenda-builder/SKILL.md

meeting-agenda-builder

Skill0 starsChanged 8 months agoMITView on GitHub

Creates structured meeting agendas with time allocation, talking points, desired outcomes, and participant roles for any CS meeting type. Adapts format by meeting type and audience. Use when asked to build a meeting agenda, structure a customer call, plan a QBR agenda, prepare a kickoff meeting structure, or when a CSM needs to ensure a meeting has a clear purpose and structure before it happens. Also triggers for questions about meeting structure, agenda creation, time allocation for calls, QBR agendas, or how to run an effective customer meeting.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

Files
SKILL.md

Meeting Agenda Builder

Creates structured agendas that ensure every meeting has a purpose, a plan, and a defined outcome. The difference between a productive 30-minute call and a wasted 30-minute call is almost always whether someone built an agenda.

How to Use

Provide:

  • Meeting type (check-in, QBR, kickoff, escalation review, renewal, executive, ad hoc)
  • Duration (how long you have)
  • Attendees (customer and internal, with roles)
  • Objective (what success looks like when the meeting ends)
  • Topics to cover (what needs to be discussed)
  • Open items from prior meetings (commitments to close the loop on)

Agenda Templates by Meeting Type

Check-In Call (20-30 min)

BlockTimeContentPurpose
Opening2 minBrief rapport. Reference something specific from the last interactionShow you remember. Set a human tone
Account observation5 minOne specific data point or observation about their accountDemonstrate you are paying attention. Open the conversation with value
Their update10 min"What is on your mind? Anything changed since we last spoke?"Let them set the direction. The most important insights come from the customer talking, not from you presenting
Your topics8 min1-2 items you need to cover (open items, upcoming events, specific questions)Cover what you planned. Keep it focused -- 2 topics maximum
Next steps3 minConfirm actions, set next touchpointAccountability. Nothing leaves the meeting without an owner and a date

QBR (45-60 min)

BlockTimeContentPurpose
Agenda review2 minWalk through the agenda. Ask if the customer wants to add anythingAlignment. The customer should feel ownership of the meeting
Value review10 minHeadline metrics, outcomes achieved, ROI evidenceJustify the investment. This is the most important section for renewals
Usage and adoption10 minWhat they are using, what they are not, peer benchmarksIdentify adoption opportunities. Drive deeper engagement
Support summary5 minTicket activity, resolution times, open issuesAccountability. Address any service gaps before they raise them
Looking ahead10 minProduct roadmap (relevant items), adoption recommendationsForward-looking. Show that the product is evolving in their direction
Strategic discussion15 minOpen floor. Their priorities, concerns, questions, feedbackThe highest-value block. Insights from this discussion shape the next quarter's account strategy
Action items5 minCapture every commitment with owner and deadlineAccountability. The QBR is only as valuable as the follow-through

Kickoff Meeting (45-60 min)

BlockTimeContentPurpose
Introductions5 minEveryone introduces themselves and their roleEstablish the team on both sides
Customer goals15 min"Why did you choose this product? What does success look like in 90 days?"The most important block. Everything else builds on their stated goals
Product overview10 minWhat they have access to and how it maps to their goalsConnect features to outcomes, not features to features
Onboarding roadmap10 minThe plan: phases, milestones, timeline, responsibilitiesSet expectations. Both sides need to understand what is required
Roles and communication5 minWho is responsible for what. Preferred communication channels. Meeting cadencePrevent ambiguity. "Who do I call if X happens?" should be answered here
Questions and next steps5 minOpen floor, then confirm the first milestone and next touchpointMomentum. The kickoff should end with a clear first action

Escalation Review (20-30 min)

BlockTimeContentPurpose
Status update5 minLead with what has been done since the last conversation. Do not make them askAccountability. Show progress before they ask about it
Current state5 minWhere things stand now. What is resolved, what is notTransparency. Do not overstate progress or understate remaining work
Resolution plan10 minWhat happens next, timeline, who is responsibleCommitment. Specific actions with dates
Customer concerns5 min"Is there anything else we have not addressed?"Space for them to raise what matters to them, not just what you planned to discuss
Next check-in2 minWhen the next update will come. Do not make them chaseProactive communication. They should never have to ask for an update

Executive Meeting (25-30 min)

BlockTimeContentPurpose
Purpose2 minWhy this meeting is happening. One sentenceExecutives have no patience for ambiguity
Your perspective5 minValue delivered, partnership highlights, forward viewEstablish the relationship's health and trajectory
Their perspective10 min"What are your priorities? How does this investment fit?"The most valuable block. Listen more than you talk
Alignment5 minConnect your roadmap to their stated prioritiesStrategic partnership, not vendor reporting
Next steps3 minOne specific follow-up. Not a list -- one thingExecutives commit to one thing. Make it count

Agenda Design Principles

PrincipleWhat It Means
Every block has a purposeIf you cannot state why a block exists in one sentence, cut it
Time allocation reflects priorityThe block you care most about gets the most time. Do not give 15 minutes to status updates and 5 minutes to strategic discussion
Customer talk time > your talk timeAim for 60/40 customer-to-CSM talk ratio. If you are talking more than them, you are presenting, not conversing
Open items are addressed, not avoidedIf something was committed in the last meeting, it appears in this meeting. Skipping open items signals they were not important
The agenda is shared before the meetingSend the agenda at least 24 hours in advance. Let the customer add topics. This signals respect and invites engagement
End with clear next stepsNo meeting should end with "we will be in touch." Every meeting ends with: who does what by when, and when do we next speak

Output Format

## Meeting Agenda: [Account Name]
**Date:** [date] | **Duration:** [minutes] | **Type:** [type]
**Attendees:** [list]
**Objective:** [one sentence -- what success looks like]

| Block | Time | Content | Notes |
|-------|------|---------|-------|
| [block] | [min] | [content] | [prep needed or context] |

**Open items from prior meeting:**
- [item 1 -- status]
- [item 2 -- status]

**Desired outcome:**
[One sentence: what you want to walk away with]

Quality Gates

  • Does the agenda have a stated objective? "Check-in with Acme" is not an objective. "Confirm Tom supports the renewal and identify any outstanding concerns" is
  • Is the time allocation realistic? A 30-minute meeting with 6 blocks of 10 minutes each does not work. Add up the minutes before sharing
  • Is the customer's voice represented? If every block is you presenting and none are the customer talking, the agenda is a monologue plan, not a meeting plan
  • Are open items from the prior meeting included? If you skip accountability, you train the customer that commitments are optional

Principles

  • An agenda is a hypothesis, not a script. The customer may take the conversation in a different direction. That is fine -- the agenda ensures you have a starting point and a fallback if the conversation stalls
  • Shorter meetings with clear agendas outperform longer meetings without them. A focused 20-minute call with a 4-block agenda creates more value than an open-ended 60-minute call with no structure
  • The agenda should be shared, not imposed. "Here is what I planned to cover -- what would you add?" signals partnership. "Here is the agenda" signals control
  • Meeting preparation and agenda building are the same activity. If you build the agenda and realise you do not know what to talk about, you need more preparation, not less structure

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.