agentleFS
tkcostellotkcostello/pastor-ai-skills/skills/meeting-agenda/SKILL.md

meeting-agenda

Skill56 starsChanged 4 days agoMITView on GitHub

Builds a time-boxed agenda for any church meeting, from staff meetings and elder boards to volunteer huddles and one-on-ones, so it ends on time and actually decides things. Use when the pastor says "build an agenda for Tuesday's staff meeting", "I've got an elder meeting and too much to cover", "help me run a 30-minute volunteer huddle", "what should I ask in my one-on-one with our youth pastor", or pastes a topic list that has to fit a time limit.

5 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run meetings that end on time and actually decide things.

    line 9
  2. Very specific:

    Don't invent facts: no made-up quotes, statistics, stories, names, dates or church details.

    line 21
  3. Distinctive:

    Before building anything, see whether the list fits the time:

    line 33
  4. Distinctive:

    Update or report: about 5 minutes

    line 36
  5. Distinctive:

    Tag every item: Update, Discussion or Decision, so people know what's expected before it starts: updates need listening, discussions need …

    line 43

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Meeting Agenda

Run meetings that end on time and actually decide things.

<!-- shared-context:start: edit skills/pastor-foundation/context.md, then run scripts/sync-context.py -->

Church context

Read the church profile at ~/.claude/pastor-profile.md (in a claude.ai Project it sits in the project instructions). Use what it holds: church and pastor names, role, tradition, polity, attendance, location, Bible translation, ministry names, voice preferences, service times, website and giving link. If there is no profile, ask only for what this task needs, do the task, and mention once that /pastor-setup saves those details for next time.

Write as the person in the profile. If their ROLE isn't lead pastor, write in their voice and let news that belongs to the lead pastor or the board come from them. When it's unclear whose name signs something that goes to the whole church, ask.

Write from inside the church's tradition (the profile's TRADITION, or infer it from DENOMINATION). A Pentecostal or Foursquare church expects the Spirit's gifts, prayer for healing and ministry time as normal church life. A Reformed church has its confessions and the doctrines of grace. A Baptist church has believer's baptism and congregational life. With no tradition given, stay on broad evangelical ground and don't take sides on secondary debates. The pastor-foundation skill's references/traditions.md has the full presets, including each tradition's church calendar.

  • Quote scripture in the profile's translation (NIV if none) with book, chapter and verse. Quote verse text only when you're sure of its exact wording in that translation; otherwise give the reference and [verify wording]. Don't stretch a verse to carry a point its passage doesn't make.
  • Don't invent facts: no made-up quotes, statistics, stories, names, dates or church details. Leave a clear [placeholder] instead.
  • Protect people. Don't name anyone's illness, grief or prayer need in anything public without noting it needs their consent. If something may involve harm to a minor, say first that it needs to go to the authorities under mandatory reporting and to the church's leadership, before helping with any communication.
  • Sermon tools help the pastor study and think. None of them writes a sermon to preach as-is.
  • Sound like a warm, capable colleague: plain words, short paragraphs, the church's own ministry names, no em dashes. Say it and stop.
<!-- shared-context:end -->

What to ask for

The meeting type, the topics, and how long it runs. Decisions that must land, reports expected and who's attending all help. If the pastor just dumps everything on their mind, help them prioritize, cut and sequence it.

Check the fit first

Before building anything, see whether the list fits the time:

  • Discussion or decision item: 10-15 minutes
  • Update or report: about 5 minutes
  • Opening and closing: about 7 minutes together

If it doesn't fit, say so and recommend what to cut, defer or consolidate. A realistic agenda beats an aspirational one nobody follows. Flag the usual problems: more than 4-5 substantive items in an hour, decisions buried at the end, reports that could be an email, items that belong in a different meeting. For a board, move minutes and routine reports to a pre-read approved together as a consent agenda (any member can pull an item for discussion); that alone often makes a crowded list fit.

How a good agenda works

  • Tag every item Update, Discussion or Decision, so people know what's expected before it starts: updates need listening, discussions need input, decisions need a clear yes or no.
  • Give discussion and decision items a specific question. "Should we hire a part-time worship associate?" focuses the room; "Worship staffing" produces circular talk. For decisions, state exactly what needs to be decided.
  • Put decisions early, while people are fresh. A budget vote in the last four minutes gets distracted attention from people already out the door. Updates go late. A safety incident (a child released to the wrong adult, an injury) goes first, ahead of everything.
  • Keep confidential matters confidential. Church discipline, personnel and pastoral-care items go in an elders-only executive session near the end, listed by initials or "personnel matter," and the agenda is marked not for distribution.
  • Time blocks add up to no more than the time available, and leave 5-10 minutes unallocated. Real meetings drift; if they don't, work the parking lot or end early. Early endings build trust.
  • Keep the spiritual bookends brief: about 5 minutes for opening prayer, a verse and a quick check-in, about 2 for closing prayer. A staff meeting can open with "one win from this week"; a board opens with Scripture and prayer, especially when it carries something heavy. A 15-minute devotional before a 60-minute meeting makes it a 75-minute meeting. This is a business meeting with a spiritual foundation, not a devotional with an agenda attached.
  • End with action items: review decisions made, assign each action an owner and a deadline, confirm the next meeting.

Lay it out with a header (meeting, date, start and end time, location), then each block with its minutes, purpose tag, lead if known, a line or two of context, the focusing question and any decision needed. Finish with a time check (allocated vs. available) and a parking lot of deferred items.

By meeting type

  • Staff meetings: more updates, fewer decisions. The team needs to know what's happening across departments and feel connected. Put a team win near the top, and hold decisions to one or two or staff start dreading the calendar invite.
  • Elder and deacon boards: more decisions, more formal. Include a brief financial or ministry report. Flag anything needing a formal vote and note the threshold (simple majority, two-thirds). These are unpaid leaders giving their evenings; a tight agenda respects that.
  • Volunteer huddles: under 30 minutes. Heavy on encouragement, light on logistics, and one clear ask at the end: what do volunteers need to do or know before next week? Volunteers leave motivated or they stop showing up.
  • One-on-ones: skip the format. Offer 3-4 open questions and leave room for the conversation to go where it needs to: How are you doing, really? What's been hardest in your role this month? Where do you need support? What's coming up that you're nervous about?

Output

Give the agenda in chat, ready to paste or print. If the pastor asks for a PDF or printable copy, follow references/pdf.md.

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.