meeting-agenda
Use when planning or preparing any church meeting: staff meetings, elder or deacon boards, committees, volunteer huddles, or one-on-ones, or when a topic list needs to fit a time limit.
tkcostello · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add tkcostello/pastor-ai-skills --skill meeting-agenda技能说明
name: meeting-agenda description: Use when planning or preparing any church meeting: staff meetings, elder or deacon boards, committees, volunteer huddles, or one-on-ones, or when a topic list needs to fit a time limit. argument-hint: "[meeting type and topics]"
Meeting Agenda Builder
Run meetings that end on time and actually decide things.
Before writing: follow the pastor-foundation skill and load the church profile from
~/.claude/pastor-profile.md. If the profile file is missing, run the pastor-setup skill first.
What You Need to Provide
To build your agenda, give me the following:
- Meeting type: Staff meeting, elder/deacon board, volunteer huddle, committee, or one-on-one
- Topics or items to cover: List everything you want to address
- Time available: Total meeting length (example: "60 minutes")
- Optional: Decisions that must be made, reports expected, people attending
The more context you give, the tighter the agenda. If you're not sure what you need, list your topics and I'll help you shape it.
Step 1: Assess and Prioritize
Before building the agenda, I evaluate whether your items fit your time.
Rule of thumb:
- Discussion or decision item: 10-15 minutes each
- Update or report: 5 minutes each
- Opening and closing: 7 minutes combined (non-negotiable)
If your list doesn't fit, I'll flag it and recommend what to cut, defer, or consolidate. The goal is a realistic agenda, not an aspirational one nobody follows.
Common problems I'll flag:
- More than 4-5 substantive items in a 60-minute meeting
- Decision items buried at the end where time always runs out
- Reports that could be sent via email instead of discussed live
- Items that belong in a different meeting type entirely
Step 2: Build the Agenda
Every agenda follows this format:
## [Meeting Type] Agenda
**Date:** [date]
**Time:** [start] - [end] ([total] minutes)
**Location:** [if provided]
---
### Opening (5 min)
- Opening prayer / brief devotional with scripture suggestion
- Quick check-in: "What's one win from this week?"
### [Topic 1] (XX min)
**Purpose:** [Update / Discussion / Decision]
**Lead:** [who owns this, if known]
- [Key context in 1-2 sentences]
- **Discussion question:** [specific question to focus conversation]
- **Decision needed:** [Yes or No. If yes, state exactly what needs to be decided.]
### [Topic 2] (XX min)
**Purpose:** [Update / Discussion / Decision]
**Lead:** [who owns this, if known]
- [Key context in 1-2 sentences]
- **Discussion question:** [specific question to focus conversation]
- **Decision needed:** [Yes or No. If yes, state exactly what needs to be decided.]
### Action Items and Next Steps (5 min)
- Review decisions made in this meeting
- Assign action items with owners and deadlines
- Confirm next meeting date
### Closing (2 min)
- Closing prayer or brief word of encouragement
---
**Time check:** [Total allocated vs. available]
**Parking lot:** [Items deferred to a future meeting]
Design Rules
These rules apply to every agenda I build. No exceptions.
Tag every item. Each agenda item gets one label: Update, Discussion, or Decision. This tells everyone what's expected of them before the item starts. Updates require listening. Discussions require input. Decisions require a clear yes or no at the end.
Decision items get discussion questions. Vague agenda items produce circular conversation. A specific question focuses the room. "Should we hire a part-time worship associate?" is better than "Worship staffing discussion."
Build in a buffer. Every agenda leaves 5-10 minutes unallocated. Real meetings drift. If everything runs perfectly, use the time for the parking lot or end early. Early endings build trust.
Keep opening and closing brief. Opening prayer and a check-in take 5 minutes total. Closing prayer takes 2 minutes. This is a business meeting with a spiritual foundation, not a devotional with an agenda attached.
Time blocks must add up. Every item gets a time allocation. Total allocated time must be equal to or less than the available meeting time. If it doesn't fit, something gets cut.
Put decisions early, not last. High-stakes decisions belong in the first half of the meeting when everyone's focused and energy is high. Reports and updates go at the end.
Meeting Type Adjustments
Staff Meetings
More updates, fewer decisions. The team needs to know what's happening across departments and feel connected. Include a team win near the top. Limit decisions to 1-2 items per meeting or staff starts dreading the calendar invite.
Elder and Deacon Boards
More decisions, formal process. Include a brief financial or ministry report. Flag any items that require a formal vote and note the vote threshold (simple majority, two-thirds, etc.). Elders and deacons are giving their time as unpaid leaders. Respect that with a tight agenda.
Volunteer Huddles
Under 30 minutes, every time. Load it with encouragement and keep logistics light. One clear ask at the end: what do you need volunteers to do or know before next week? Volunteers leave motivated or they stop showing up.
One-on-Ones
Skip the rigid format. Use 3-4 open-ended check-in questions and leave space for the conversation to go where it needs to go. Suggested questions: How are you doing, really? What's been the hardest part of your role this month? Where do you need support? What's coming up that you're nervous about?
Anti-Patterns I Will Never Build
Fifteen items for a 60-minute meeting. This is not an agenda, it is a wish list. Items will get cut on the fly, nothing will get proper time, and the meeting will run long anyway. Pick the top 5 and defer the rest.
No time allocations. An agenda without time blocks is a list. Time blocks communicate priority, keep the facilitator accountable, and give attendees a clear read on whether a discussion is going long.
**Import
阅读完整来源 ↗