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.
Joseph's sermons start as raw voice dictation. Expect:
These apply to every sermon, every pass. Cross-reference writing for general editing principles.
niv-bible-fetch skill to verify.Read the entire file. Identify which sections are polished and which are fresh raw dictation. Map the sections by theme. Note any theological distinctions Joseph is developing — these get preserved and sharpened, not cut.
Identify 4-6 major sections. Name each with a clear, short title. Each section should be ~5 minutes of delivery.
Typical sermon structure:
For sections that are fresh voice-to-text:
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.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:
Load and follow the writing skill. Sermons are especially vulnerable to:
After all other editing is done, grep the file for em-dashes (U+2014). Replace every instance except those inside NIV scripture block quotes. Common replacements:
Sermons go to: wiki/produce/hermes/sermons/
Filename: title-slug-book-chapter.md (e.g., go-before-you-know-1-samuel-16.md)
When Joseph asks to review and improve an existing sermon section by section:
1. Read the full sermon first for context. Never edit a section in isolation — the whole must stay coherent.
2. Go section by section. For each section, check: grammar, theology, flow/transitions, NIV accuracy, footnotes.
3. Create a v2 file (*-v2.md) alongside the original. Do not modify the original during editing.
4. Blog formatting: If publishing on jjude.com, drop unnecessary section titles (e.g., "## Introduction" — the reader doesn't need to be told). Keep structural headings only when they genuinely organize content.
5. Transitions between paragraphs: If there's a jump between ideas (e.g., from a theological point to a supporting reference), add a short bridging sentence rather than leaving the cut abrupt.
KJV creep affects not just the main blockquote but every verse quoted within the body text. Scan ALL scripture quotations, including casual references inside paragraphs. Common KJV-to-NIV fixes:
Use BibleGateway.com with version=NIV to verify every verse, not just the ones that look wrong.
Sermons are often developed in multiple passes:
1. First pass: Joseph shares raw notes, you structure and clean
2. Joseph edits, rearranges, adds new raw dictated sections
3. You clean the new sections, remove em-dashes, polish
4. Repeat until preach-ready
Each pass, read the FULL file (not just the new parts) to catch inconsistencies between polished and raw sections.
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 — including verses quoted casually inside paragraphs, not just the main blockquote. Do a final pass replacing any KJV phrasing throughout the entire text.
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").
6. Em-dashes slipping through. Joseph banned em-dashes in all writing. Always do a final grep for U+2014 after editing. The only acceptable em-dash is inside a direct NIV scripture quotation where the verse itself uses one.
7. Flattening theological distinctions. When Joseph develops a multi-part theological framework (e.g., knowledge → insight → discernment, or the cost of obedience), preserve the structure and sharpen the language. Do not merge the parts into a vague paragraph. These distinctions are what make the sermon teach, not just inspire.
8. Flowing examples through multi-part concepts. When explaining a concept with multiple stages (knowledge → insight → discernment), use ONE example that flows through all three stages rather than a different example for each. A single story (e.g., Psalm 23: reciting it = knowledge, understanding what 'he makes me lie down' means = insight, choosing to rest when exhausted = discernment) is more cohesive and memorable than three unrelated examples. If using multiple examples, ensure they are from the same world (e.g., all construction site, all medical) so the congregation follows one thread.
9. Two audiences. Joseph writes sermons in English for professionals (blog) but preaches in Tamil to daily labourers. Same sermon structure, different examples. When Joseph asks for examples, clarify which audience before writing.