Back to catalog
Skills / Writing / sermon-writing

sermon-writing

Write sermons from voice notes. NIV, preach-voice.

Category ✍️ Writing
Version v1.0.0
writingsermonpreachingbiblescripturenivchurch

Sermon Writing

Write sermons from Joseph's raw voice-dictated notes into structured, preach-ready manuscripts. Sermons are a distinct class from blog posts — different voice, structure, and constraints.

When to Use

  • Joseph shares rough sermon notes (voice-to-text, bullet points, stream-of-consciousness)
  • Joseph asks to structure, clean up, or edit a sermon draft
  • Joseph asks to convert sermon notes into a timed delivery (~30 min or other)

Source Material

Joseph's sermons start as raw voice dictation. Expect:

  • Repeated points (he circles back for emphasis)
  • Conversational tangents that are preaching moments, not noise
  • Scripture references mixed with personal commentary
  • "So that is important" and similar preacher affirmations
  • Occasional speculation ("maybe five years old") that is not biblical

Workflow

1. Identify Sections

Read the raw notes. Identify 4-6 major sections. Name each with a clear, short title. Each section should be ~5 minutes of delivery. Mark time estimates.

Typical sermon structure:

  • Introduction (hook + scripture reference + preview)
  • 3-6 body sections (each with scripture, exposition, application)
  • Summary (brief recap of key points)
  • Action steps (3-5 concrete takeaways)

2. Write in Preach-Voice

Sermon voice is NOT blog voice. Key differences from the blogging skill:

Pronouns: Sermons use "you" and "we." This is speaking TO a congregation, not writing about yourself. "You are mourning" not "I was mourning." "We need to pray" is acceptable. Scripture: Always in italics ("text"). Always NIV. Always cite book chapter:verse. Repetition: Some repetition is good in sermons. It's a preaching technique, not filler. But cut genuine redundancy, not rhetorical emphasis. Tone: Direct, warm, authoritative. Like a pastor talking to his congregation. Not academic, not blog-casual.

3. Scripture Verification

ALL Bible verses must be NIV. Use the niv-bible-fetch skill to verify from BibleGateway.com. Never use KJV, ESV, or other translations.

Common patterns in Joseph's notes — the KJV phrasing he uses mentally needs NIV replacement:

  • "Yea, though I walk through the valley of the shadow of death" → "Even though I walk through the darkest valley"
  • "Thy word is a lamp unto my feet" → "Your word is a lamp for my feet"
  • "The Lord seeth not as man seeth" → "The Lord does not look at the things people look at"
  • "preparest a table before me" → "You prepare a table before me"

4. Apply Anti-Slop Rules

Load and follow the no-ai-slop skill. Sermons are especially vulnerable to:

  • "That is the prescription" type filler (cut it)
  • Speculative claims not in scripture (e.g., "maybe five years old" — drop it)
  • Over-explaining ("That is what happens when..." — trust the congregation)
  • Faux-insight setups ("Here's the thing about this passage...")

5. Persist to Wiki

Sermons go to: wiki/produce/hermes/sermons/

Filename: title-slug-book-chapter.md (e.g., go-before-you-know-1-samuel-16.md)

Pitfalls

1. Speculative claims about scripture. If the Bible does not say Samuel was five when he started ministering, do not add "maybe five years old." Stick to what scripture says. "Samuel had served the Lord since childhood" is stronger and accurate (1 Samuel 2:18). When in doubt, check the text.

2. KJV creep. Joseph's mental scripture is often KJV from years of hearing it. Every verse in the output must be NIV. Do a final pass replacing any KJV phrasing.

3. Blog voice vs. preach voice. Do NOT write a sermon in blog I-voice ("I believe," "I observed"). Preaching is direct address. Use "you" and "we." The one exception: Joseph's personal stories or observations, which stay in I-voice ("Samuel was not seeking God...").

4. Over-polishing the raw notes. Joseph's dictation has preaching rhythm. Do not flatten it into essay prose. Keep the conversational warmth. Cut genuine slop but preserve the preacher's cadence.

5. Missing action steps. Sermons should end with 3-5 concrete things the congregation can do. Not abstract ("be faithful") but specific ("Set aside time this week for worship before you scroll your phone").

Anti-Slop Checklist (Sermon-Specific)

  • [ ] No "That is the prescription/formula/answer" type declarations
  • [ ] No speculative claims not grounded in scripture text
  • [ ] No "Here is what I love about this passage" setups (state the point directly)
  • [ ] No faux-insight ("The part that matters most...")
  • [ ] All verses verified NIV against BibleGateway
  • [ ] No KJV phrasing remaining
  • [ ] Action steps are specific, not abstract