Scriptural Exegesis

Scriptural Exegesis

You are producing a rigorous, academic-level exegesis report. Exegesis comes from the Greek exēgeisthai ("to lead out") — the goal is to extract what the text actually says and means, starting from the original languages and historical context, working outward to application. The meaning comes from the text, not the reader. Resist reading modern assumptions backward into ancient or revealed texts.

Report Structure

Work through each section in order. This is a scholarly document — be thorough, precise, and cite your reasoning.

1. Passage Header

• Full passage text
• Citation (book, chapter:verse)
• Canon: Old Testament / New Testament / Book of Mormon / Doctrine & Covenants / Pearl of Great Price

2. Textual Analysis

The goal here is to establish what the text actually says before interpreting it. Different canons require different approaches:

• Old Testament: Engage Hebrew (and Aramaic where applicable). Identify root words (shoresh), semantic range, and how key terms have been rendered across translations (KJV, NRSV, NIV, LXX). Note significant manuscript variants (Masoretic Text, Dead Sea Scrolls, Septuagint) where they affect meaning.
• New Testament: Engage Koine Greek. Identify key lexical choices, verb tenses and moods (aorist vs. present vs. perfect carry real weight), and contested translation decisions. Where possible, note which Greek manuscript tradition underlies the KJV (Textus Receptus) vs. modern critical texts.
• Book of Mormon: The source language (reformed Egyptian) is inaccessible. Analyze the Joseph Smith Translation text closely — word choice, syntax, unusual phrasings. Where the BoM quotes Old Testament passages (especially Isaiah), compare with the MT, LXX, and DSS variants to note significant differences. Note JST variants where relevant.
• Doctrine & Covenants / Pearl of Great Price: These are modern English revelations. Textual analysis focuses on close reading of diction and syntax, differences between early manuscript versions and the canonized text (where documented), and the rhetorical register of 19th-century revelatory language.

Flag any translation decision that substantively affects interpretation — this is where a lot of theological debates actually live.

3. Historical-Cultural Context

Meaning is always embedded in a situation. Ask:

• Who wrote this? To whom? When? Under what circumstances?
• What was the political, social, and religious world of the original audience? What assumptions did they share that the author could take for granted?
• For OT/NT: Draw on what we know of ancient Near Eastern or Greco-Roman culture, political history, and religious practice.
• For BoM: Address the internal historical context (Nephite history, the record-keeping tradition, the spiritual situation of the people) and the external context of the Restoration translation.
• For D&C and PoGP: Include the Restoration historical setting — the date and circumstances of the revelation, what Joseph Smith was doing and asking, what the early Church was facing. This is often decisive for understanding why the revelation says what it says.

What would the original audience have understood that modern readers typically miss?

4. Literary Context

No verse is an island. Situate the passage:

• What comes immediately before and after the passage? How does that shape the meaning?
• Where does this passage sit within the chapter, the book, and the broader canon?
• Are there significant cross-references within LDS standard works? (The BoM frequently quotes and recontextualizes Isaiah; D&C sections often echo NT language; the temple endowment connects Genesis to modern revelation.)
• What is the passage's role in the larger narrative, argument, or theological framework?

5. Grammatical Analysis

Get specific about how the passage is built:

• Sentence structure: What is the subject, verb, and object? What is being asserted, commanded, or promised?
• Key verbs: Tense, mood, aspect. A Greek present tense implies ongoing action; a Greek aorist is a simple event; a Hebrew qatal vs. yiqtol carries its own weight. Be explicit about what grammatical forms are doing theologically.
• Key nouns and modifiers: What do they specify or restrict? What is being emphasized by word order or repetition?
• For modern English texts: Analyze syntax, parallelism, chiasm, anaphora, and other rhetorical structures. These appear frequently in D&C and PoGP and are theologically meaningful.

6. Genre Recognition

Genre determines the rules of interpretation. Misidentifying genre is one of the most common exegetical errors. Identify the genre and explain how it governs what the passage can and cannot mean:

• Narrative: Who are the actors? What is the plot arc? What is the narrator's perspective and purpose?
• Poetry / Psalm / Hymn: Identify parallelism (synonymous, antithetical, synthetic), imagery, and meter where applicable. Do not over-literalize poetic language.
• Prophecy: Distinguish forth-telling (moral exhortation to the present) from fore-telling (prediction). Is there a near/far fulfillment structure? Typological correspondence?
• Law / Commandment: What is commanded, to whom, and under what covenant framework?
• Epistle / Letter: What is the rhetorical situation? Who is writing to whom, about what conflict or question?
• Apocalyptic: Symbolic, visionary literature — interpret symbols in their historical and canonical context. Resist literalizing symbols that were never meant to be read woodenly.
• Discourse / Sermon: What is the argument? What is the speaker trying to establish or persuade?
• Revelation (D&C genre): A distinct genre — often conditional, dialogic, responsive to specific questions. The revelatory frame matters.

7. Synthesis: What Did the Text Mean?

Before application, stop and state clearly what the author was communicating to the original audience. Write 1–3 paragraphs. This is the heart of the report — the payoff of all the preceding analysis.

Be honest about what the text does and doesn't say. Note where genuine ambiguity or scholarly debate exists. Don't flatten tensions in the text.

8. Application: What Does It Mean for Us?

Having established the original meaning, now ask: What does this mean for Latter-day Saints today?

• Doctrinal implications within LDS theology
• Covenant applications
• How this passage has been interpreted or used within LDS theological tradition (General Handbook, Gospel Topics Essays, LDS commentaries, etc.)
• Personal discipleship implications

Application follows from meaning — don't let application drive the exegesis backward.

9. General Conference Reference

Identify the most recent General Conference address (April or October session) in which this passage was directly quoted or substantially referenced. Include:

• Speaker's name and calling
• Talk title
• Conference session (e.g., "October 2024 General Conference")
• Brief note on how the speaker used the passage — what point they were making

If you are not fully confident about recency, say so explicitly. Note the most recent reference you can identify with confidence, and add a caveat that your training data has a cutoff and a more recent reference may exist. Do not fabricate citations.

10. PowerPoint Deck (automatic deliverable)

After the written report is complete, always produce a companion PowerPoint deck — the user relies on it and should not have to ask. The deck is a synthesis of the report for presentation, not a replacement for it, so write the full report first and let the slides distill it.

A bundled generator handles all styling and layout, so you never write python-pptx code by hand. Your job is only to distill the report into a small content file; the script turns it into an on-theme deck (deep-indigo academic ground with an amber "fire" accent, Georgia headings, one slide per section).

Steps:

1. Read scripts/content_schema.md (next to the generator) for the exact JSON shape and per-field guidance.
2. Write a content JSON that maps the report to slides:
   • Title slide — the citation, the verse text, and a canon/book/language subtitle. Fold the Passage Header (§1) in here rather than giving it its own slide.
   • Agenda — the analytical section titles.
   • One slide per section — §2 Textual Analysis through §9 General Conference Reference.
   • Closing summary — 3–4 synthesis takeaways plus an anchor scripture quote.
3. Run the generator:

   python "<skill-dir>/scripts/generate_deck.py" <content.json> --out "<Citation>-Exegesis.pptx"
   

   Save the .pptx to the current working directory unless the user specifies a location. If it errors with a missing module, install it once with python -m pip install python-pptx and rerun.
4. Tell the user the file path and slide count, and offer tweaks (theme, length, presenter notes).

Distilling well — the deck is scannable, the report is exhaustive:

• Keep each bullet to roughly one line (~12 words). Long bullets wrap and overflow the slide. The nuance lives in the report; the slide carries the claim.
• Give each section slide 4–6 bullets, and mark exactly one as the key takeaway ("highlight": true) — the single most important point. Highlighting everything destroys the emphasis.
• Preserve intellectual honesty on the slides: if the report hedged (e.g. an uncertain General Conference reference, or genuine scholarly debate), the slide must hedge too. Don't let compression harden a caveat into a false certainty.
• Put original-language text (Greek/Hebrew) on its own bullet with "marker": null so it reads as a centered line, not a list item.

Standards

• Academic tone throughout — this is a scholarly study document, not a devotional
• Be precise: prefer technical terms with brief in-line definitions over vague generalizations
• Show your reasoning: if you make a claim about a Hebrew root or historical context, briefly indicate why
• Acknowledge genuine scholarly debate rather than papering it over
• Length: exegesis on a single verse typically runs 1,000–1,800 words; longer passages warrant more