Pastoral Prayer
When the user specifies a scenario (e.g. illness, thanksgiving, worship, funeral, wedding, baptism), produce one complete prayer. Output in English only. Default output is plain text; use Markdown or DOCX only if the user requests it.
Defaults and overrides
- Tradition: Evangelical unless the user specifies Reformed, Charismatic, Baptist, Non-denominational, or other. Avoid sect-specific jargon unless the user has specified a tradition.
- Output format: Plain text by default; offer or use Markdown/DOCX only when the user asks.
Shared guidelines
- Tone: dignified, gentle, reverent; clear and restrained; no mystical or esoteric language.
- Where phrasing goes beyond clear biblical language, label it Reference application / not direct scripture (e.g. in a short note after the prayer or in brackets only if necessary for transparency).
- Doctrine: avoid occult, extreme declarations, unorthodox terminology.
Output
- One complete prayer text: address to God, thanksgiving or context, petitions, and closing (e.g. in Jesus’ name, Amen).
- Length: suitable to be read aloud in 1–2 minutes unless the user asks for shorter or longer.
- Use “you”/“your” for God; avoid overly informal or theatrical language.
Rules
- Prayers must be theologically sound and consistent with orthodox Christian belief.
- Do not assume denominational specifics (e.g. baptism mode, Lord’s Supper theology) unless the user specifies a tradition.
- The prayer should be usable as-is or with minimal editing in the stated scenario (hospital, worship service, funeral, wedding, etc.).
- If a phrase is inferred from general biblical themes rather than a direct quote, avoid overclaiming; optional note: (Reference application) for transparency.
Before use (funeral, wedding, and other personal occasions)
For funeral, wedding, baptism, or other highly personal settings, the pastor should tailor the wording before use: insert the correct names and relationships, and adjust for the congregation and culture (e.g. sensitivity to family background, local custom). Use the generated prayer as a draft, not a final script.
Example scenarios
- Illness / hospital visit
- Thanksgiving / gratitude
- Corporate worship (opening or closing)
- Funeral / memorial
- Wedding
- Baptism
- Meeting or ministry planning
- Crisis or grief
1---2name: pastoral-prayer3description: Produces full, readable pastoral prayers for specific scenarios (illness, thanksgiving, worship, funeral, wedding, baptism, etc.). Use when the user asks for a prayer for a pastoral situation. Tone dignified and gentle; theologically sound; ready to be read aloud or adapted on the spot.4---56# Pastoral Prayer78When the user specifies a scenario (e.g. illness, thanksgiving, worship, funeral, wedding, baptism), produce one complete prayer. Output in English only. Default output is plain text; use Markdown or DOCX only if the user requests it.910## Defaults and overrides1112- **Tradition:** Evangelical unless the user specifies Reformed, Charismatic, Baptist, Non-denominational, or other. Avoid sect-specific jargon unless the user has specified a tradition.13- **Output format:** Plain text by default; offer or use Markdown/DOCX only when the user asks.1415## Shared guidelines1617- Tone: dignified, gentle, reverent; clear and restrained; no mystical or esoteric language.18- Where phrasing goes beyond clear biblical language, label it **Reference application / not direct scripture** (e.g. in a short note after the prayer or in brackets only if necessary for transparency).19- Doctrine: avoid occult, extreme declarations, unorthodox terminology.2021## Output2223- One complete prayer text: address to God, thanksgiving or context, petitions, and closing (e.g. in Jesus’ name, Amen).24- Length: suitable to be read aloud in 1–2 minutes unless the user asks for shorter or longer.25- Use “you”/“your” for God; avoid overly informal or theatrical language.2627## Rules2829- Prayers must be theologically sound and consistent with orthodox Christian belief.30- Do not assume denominational specifics (e.g. baptism mode, Lord’s Supper theology) unless the user specifies a tradition.31- The prayer should be usable as-is or with minimal editing in the stated scenario (hospital, worship service, funeral, wedding, etc.).32- If a phrase is inferred from general biblical themes rather than a direct quote, avoid overclaiming; optional note: *(Reference application)* for transparency.3334## Before use (funeral, wedding, and other personal occasions)3536For funeral, wedding, baptism, or other highly personal settings, the pastor should tailor the wording before use: insert the correct names and relationships, and adjust for the congregation and culture (e.g. sensitivity to family background, local custom). Use the generated prayer as a draft, not a final script.3738## Example scenarios3940- Illness / hospital visit 41- Thanksgiving / gratitude 42- Corporate worship (opening or closing) 43- Funeral / memorial 44- Wedding 45- Baptism 46- Meeting or ministry planning 47- Crisis or grief
cheniOS