small-group-questions
Skill56 starsChanged 4 days agoMITView on GitHub
Turns Sunday's sermon into a small group discussion guide with icebreakers and 8-10 questions that move from observation to interpretation to application. Use when the pastor says "write small group questions for this week", "life group guide on Romans 8", "discussion questions from Sunday's sermon", "turn my notes into a Bible study", or "questions for our home groups".
In this repository18 other files it gives its agents.
- announcement-scriptSkill
- church-emailSkill
- church-letterSkill
- church-social-postSkill
- funeral-prepSkill
- meeting-agendaSkill
- midweek-devotionalSkill
- pastor-foundationSkill
- pastor-setupSkill
- sermon-brainstormSkill
- sermon-feedbackSkill
- sermon-researchSkill
- sermon-seriesSkill
- sermon-to-blogSkill
- sermon-to-youtubeSkill
- social-media-calendarSkill
- sunday-to-weekSkill
- wedding-prepSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
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
- Very specific: line 21
Don't invent facts: no made-up quotes, statistics, stories, names, dates or church details.
- Distinctive: line 51
Keep the order: observation, interpretation, application.
- Distinctive: line 53
Write for the group, not a seminary class.
- Distinctive: line 54
Don't lean on feelings questions.
- Distinctive: line 55
Every question works for someone who missed Sunday.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
Small Group Discussion Questions
Sunday's sermon becomes the week's small group conversation.
<!-- 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 passage is enough for solid questions. Sermon notes, an outline, a transcript, the big idea or an application emphasis make the guide track what was actually preached. Use the date if given.
Find the core first
Before writing questions, pin down the sermon's big idea in one sentence (a point, not a topic: "God's faithfulness in the wilderness is the reason you can trust him in yours," not "God is faithful"), its 2-3 key themes, and the main thing it called people to do or believe. Stay in the lane the sermon opened. If it was about forgiveness and never touched justice, leave justice alone.
The guide
Head it with the week, passage and big idea, then:
- Icebreaker, two options so the leader can fit the group (a 6 AM men's group and a Thursday couples' group need different doors in). One light, answerable by anyone who has never opened a Bible; one more reflective that starts toward the topic.
- Read the passage together. Give the reference only, not the printed text. Groups should open their Bibles; that habit matters. If the passage involves violence or sexual abuse, suggest which verses to read aloud and which the leader can summarize.
- Observation, 2 questions: what's on the page (people, sequence, repeated words), plus one detail that's easy to miss on a first read.
- Interpretation, 3 questions: why the author made a specific choice; a piece of cultural or historical context that changes the meaning, kept accessible; how the passage connects to the larger biblical story. Under each one, add a one-line Leader note with what the text supports, so a leader without commentaries can steer. Any contested verse the sermon touched goes here with a leader note, not in Going deeper.
- Application, 3 at most: one personal without demanding public confession ("Where do you find yourself in this story?"); one tied to work, family, money or relationships; one with some edge that presses the demand the sermon made. When one quotes a verse, use it as its passage uses it: don't lift a phrase into an application the passage doesn't make. More than three turns the room into a confession booth, and application lands harder after the text has done its work.
- Going deeper, 2 for groups that want more: a cross-reference question with the reference given, and a theological question with guardrails ("What does this text tell us about how God initiates relationship with people?" rather than "Do you believe in predestination?").
- Closing: a prayer prompt tied to what this passage demanded, not "pray for each other's needs," and one small, concrete optional challenge someone could report back on next week.
What makes the questions work
- 8-10 questions including Going deeper; the icebreakers don't count. Groups have 60-90 minutes, so every question earns its place.
- For passages involving abuse or violence, add a short leader note at the top: someone may disclose their own story, how to respond in the moment, and to bring it to the pastor afterward.
- Keep the order: observation, interpretation, application. Starting with "what should we do?" skips the work of understanding the text.
- Open-ended only. If one word answers it, rewrite it. No leading questions with one right answer ("Don't you think God was testing Abraham here?").
- Write for the group, not a seminary class. Nothing that needs Greek or a shelf of commentaries.
- Don't lean on feelings questions. "How did this make you feel?" on repeat is therapy with a Bible on the table.
- Every question works for someone who missed Sunday. The guide stands alone with only a Bible.
Output
Give the guide in chat, ready to paste or hand to leaders. If the pastor asks for a PDF or printable copy, follow references/pdf.md.
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.

