---
name: creative-first-draft-multiplier
description: Turns one finished sermon transcript, executive keynote, or leadership article into grounded first-draft derivatives (small-group discussion questions, midweek recap email, social clip hooks, and a plain-English staff summary) while keeping humans in charge of voice, theology, and final craft.
license: CC-BY-4.0
metadata:
  author: Paul Yerrick (paulyerrick.com / COKI Studio)
  version: "1.0"
  category: creative-and-communications
  source: https://www.paulyerrick.com/ai/
---

# The Creative First-Draft Multiplier

Take one finished piece of real human communication (a Sunday message transcript, executive keynote, or leadership memo) and eliminate blank-page friction by generating four grounded first drafts for your team to edit in their own voice.

## When to Use This Skill

- After a pastor, executive, or speaker has already delivered or written the core message.
- When a communications, ministry, or marketing team needs Monday morning starting drafts for small groups, email, social clips, and internal staff alignment.

## When Not to Use This Skill (Red Lines)

- **Never use this skill to ghostwrite a pastor's sermon or a leader's original convictions from scratch.** Real human thinking and embodied voice come first; this skill multiplies finished work.
- **Never invent Scripture quotes, statistics, personal stories, or theological claims** that are not present in the source transcript.
- **Never publish raw AI output.** A human editor must review every line for accuracy, theological integrity, tone, and fit before anything goes public.

## Inputs Needed

Ask the user to paste or attach:

1. **The finished transcript or manuscript** (required)
2. **Context:** Church/ministry or business/executive audience (optional, infer from transcript)
3. **Optional voice notes:** Any specific phrases your team avoids or a call to action to include in the midweek email (optional)

## Step-by-Step Instructions

1. **Stay strictly grounded in the source text.** Every takeaway, quote, Scripture reference, and clip hook must trace directly back to what the speaker actually said. If a Scripture verse or fact is referenced loosely in the transcript, flag it as `[Verify reference]` for the human editor.
2. **Preserve the speaker's actual voice.** Pull real language and memorable lines from the transcript instead of rewriting them into generic marketing clichés.
3. **Generate all four deliverables cleanly:**
   - **Deliverable A: Small-Group or Team Discussion Guide** (3 to 5 thoughtful, open-ended questions grounded in the talk, moving from observation to personal application).
   - **Deliverable B: Midweek Recap Email First Draft** (150 to 220 words, warm and human, pointing back to one core idea plus a clear placeholder for a link or next step).
   - **Deliverable C: Five Candidate Social Clip Hooks** (exact quote or moment from the transcript, suggested 1-line hook, and why it works as a 30 to 60 second clip).
   - **Deliverable D: Plain-English Staff Summary** (4 to 5 bullet points for staff or volunteers who were serving in other rooms and missed the message).
4. **Add a brief Human Verification Note** at the bottom listing any quotes, references, or names the editor should double-check before publishing.

## Output Format

Use this exact markdown structure:

```markdown
## Creative First-Draft Multiplier Pack
**Source:** [Talk or Message Title] | **Status:** First draft for human editing

### 1. Discussion Questions (Small Group / Team)
1. [Warm-up or observation question grounded in the message]
2. [Core tension or reflection question]
3. [Practical application question for this week]
4. [Optional deeper follow-up question]

### 2. Midweek Recap Email (First Draft)
**Subject line options:**
- Option 1: [Direct, non-clickbait subject]
- Option 2: [Conversational subject]

**Body:**
[150 to 220 word draft in plain, grounded language. Include [LINK] placeholder where appropriate.]

### 3. Five Candidate Social Clip Moments
1. **Hook:** "[Short 1-line hook]"
   - **Transcript anchor:** "[Exact opening phrase from transcript so video editor can find it]"
   - **Why it works:** [1 short line]
*(Repeat for 2 through 5)*

### 4. Plain-English Staff Summary (For People Serving in Other Rooms)
- **Core idea:** [1 sentence]
- **Key points:** [2 to 3 crisp bullets]
- **Call to action mentioned on stage:** [Exact next step announced, or "None mentioned"]

### 5. Human Editor Verification Notes
- [List any Scripture references, quotes, names, or dates to verify before publishing]
```

## Voice and Style Rules

- Sound like a real human leader, not an ad agency or a hype bot.
- Avoid cliché openers ("In today's fast-paced world...", "Let's dive in...", "Game-changer").
- Never use em-dashes or emojis.

## Quick-Start Example

**Example Input:**
> Paste a 3,500-word transcript of a Sunday sermon titled "Wells, Not Towers" on Daniel in Babylon, along with a note: "Keep the email warm and direct, and include a placeholder link to our Sunday message replay."

**Expected Behavior:**
Produce the 4-part pack grounded strictly in quotes and themes from the transcript, surface exact transcript phrases so the video editor can jump right to the 5 best clip timestamps, and flag every Scripture reference for human verification.
