Consult on video production: $ARGUMENTS
$ARGUMENTS should include:
- Course slug or name (e.g.,
forgotten-ways, reframation, mdna)
- Optionally: specific week or module (e.g.,
week 3, all weeks)
- Optionally: video type (opening video, explainer, promo, social cut, course trailer)
- Optionally: specific topic, theme, or scripture passage to ground in
- Empty — ask the user what course and video they're working on
Before Starting
1. Understand the Course Context
Read in this order — stop as soon as you have enough context:
- Check for existing course content in
content-library/courses/[slug]/ — read any authored weeks for theological themes, arc, and progression
- If this is the Forgotten Ways course, read
/Users/joshuashepherd/Desktop/Dev/repos/forgotten-ways-course/editor/data/course.json for canonical content
- Read
_docs/COURSE_STRATEGY.md if it exists — authoritative reference for course structure
- Read
_docs/TRANSFORMATIONAL_COURSE_CHARTER.md if it exists — the Four Necessities (dissonance, action, reflection, community)
2. Understand the Video System
- Read
_docs/videos/README.md — production workflow, project structure, current state
- Read
_docs/videos/style-guide/brand-tokens.md — colors, typography, motion tokens
- Read
_docs/videos/style-guide/motion-principles.md — easing, pacing, composition rules
- Read
_docs/videos/templates/script-template.md — canonical script format
- Read
_docs/videos/templates/storyboard-template.md — canonical storyboard format
- Check for existing scripts/storyboards in
_docs/videos/courses/[slug]/scripts/ and storyboards/
3. Understand the Shared Scene Library
Read _docs/videos/courses/_shared/scripts/course-explainer-scenes.md — the 14-scene explainer library serves as a reference for tone, structure, and visual vocabulary.
Consultation Modes
Determine which mode the user needs. If unclear, ask.
Mode A: Full Video Plan (Scripture → Arc → Storyboard → Script)
For when starting from scratch on a video. This is the primary mode.
Step 1 — Theological Grounding
Identify the scripture and theological foundations for this video:
- What is the core concept this video must land? (From the course week's teaching content)
- What scripture passages ground it? (Woven, not proof-texted — per Alan's voice)
- What historical examples illuminate it? (Early church, Chinese underground church, SMRC, Methodist movement)
- What Alan Hirsch frameworks apply? (mDNA, APEST/5Q, Shema, sentness, incarnational-missional)
- What books/chapters are the corpus sources? (Cite as: The Forgotten Ways ch3, 5Q ch7, etc.)
Output a Theological Brief — 200-400 words covering the above. This becomes the foundation everything else builds on.
Step 2 — Narrative Arc
Design the story structure for this video. Every video — whether 30 seconds or 5 minutes — has an arc.
For opening videos (weekly, ~5 min):
- Hook: name the tension or question the week confronts (15-20s)
- Core concept: plain language, first-person "we" (60-90s)
- Grounding: one scriptural or historical anchor (45-60s)
- Implication: what this means for the learner's life (30-45s)
- Invitation: closing question or anticipation for what's next (15-20s)
For explainer videos (course-level, 2-5 min):
- Use the three-act structure from the shared scene library:
- Act 1 — What transformation means (composites, tension)
- Act 2 — Why the current approach fails (data, reality)
- Act 3 — How formation works (method, the loop)
- Close — CTA
For social cuts / promos (15s-60s):
- Single tension → single insight → CTA
- Front-load the most compelling 3 seconds (the hook)
For module recaps / synthesis (1-3 min):
- What we explored → what we did → what changed → what's next
Output an Arc Document — a numbered sequence of beats with estimated duration per beat.
Step 3 — Scene Breakdown & Storyboard
For each beat in the arc, define:
| Field |
Description |
| Time |
Start–end timecode |
| Narration |
Exact voiceover text (word count noted) |
| Alan quote |
On-screen quote from published works, if applicable |
| Visual |
Detailed visual description — composition, motion, metaphor |
| On-screen text |
Any titles, labels, callouts |
| Motion |
Animation/transition description using motion-principles vocabulary |
| Assets needed |
NB2 backgrounds, illustrations, or code-only elements |
| Transition out |
How this scene exits to the next |
Use the storyboard template format from _docs/videos/templates/storyboard-template.md.
Step 4 — Script
Write the full narration script with production notes, using the script template from _docs/videos/templates/script-template.md.
Include:
- Scene-by-scene narration at ~145 wpm (cinematic, not rushed)
- Alan Hirsch quotes — properly attributed to specific books
- Production notes: key concept, corpus references, dissonance moment, call to action
- Asset requirements table
Mode B: Scripture & Theology Consult
For when the user has a video concept but needs help grounding it theologically.
- Read the video concept or existing script
- Identify theological gaps: Where is the Christocentric anchoring? Where is the scriptural grounding? Where are the historical examples?
- Suggest specific scripture passages, Alan frameworks, and historical parallels
- Rewrite or annotate sections to strengthen theological depth
- Apply the alan-voice markers: Christocentric anchoring, pastoral warmth, narrative imagery, theological depth, prophetic intensity
Output: annotated script or theological brief with specific suggestions.
Mode C: Arc & Structure Consult
For when the user has content but needs help with narrative structure.
- Read existing content (script, teaching notes, or course section content)
- Identify the narrative arc — is there a clear hook → tension → grounding → implication → invitation?
- Diagnose structural issues: Does it front-load information? Does practice appear before understanding? Does it rush to resolution?
- Propose a revised arc with beat-by-beat timing
- Flag pacing issues — are there enough breathing moments? Is the dissonance held long enough?
Output: revised arc document with structural notes.
Mode D: Storyboard & Visual Consult
For when the user has a script but needs visual direction.
- Read the script
- For each scene, propose visual concepts using the brand vocabulary:
- Warm charcoal backgrounds, gold accents, organic textures
- Abstract/silhouette figures, never photorealistic
- Typography-driven scenes vs. image-driven scenes
- Motion language from
motion-principles.md
- Identify which scenes need AI-generated assets (NB2 backgrounds) vs. code-only animation
- Write NB2 prompt anchors for any generated assets
- Note Remotion composition considerations (scene type, transition type, duration in frames)
Output: storyboard document using the canonical template.
Voice Guidelines
All narration and script content must follow Alan Hirsch's voice. The five markers:
- Christocentric anchoring (30%) — Jesus is Lord. Every framework points back to Jesus.
- Pastoral warmth (20%) — "We" language. Invitational, not prescriptive.
- Narrative imagery (15%) — Organic metaphors: movement, seeds, fire, rivers. Historical stories.
- Theological depth (10%) — Grounded in Scripture and tradition. Accessible but deep.
- Prophetic intensity (25%) — Reframing questions. Productive dissonance. Calls to risk.
Anti-patterns (never use): corporate consultant tone, detached academic voice, antithesis patterns ("Not X, but Y"), generic motivational language, bullet-point lists as primary content.
Rhetorical posture: Alan speaks from ahead — he describes what the audience doesn't yet see as though it is already visible. He challenges the frame before engaging the question within it.
Scripture usage: Woven, not leading. No sermon-like openings. No proof-texting. Scripture governs the argument but rarely opens it.
Output & File Placement
Save all outputs to the appropriate per-course directory:
| Output |
Save to |
| Theological brief |
_docs/videos/courses/[slug]/scripts/[video-id]-theology.md |
| Arc document |
_docs/videos/courses/[slug]/storyboards/[video-id]-arc.md |
| Script |
_docs/videos/courses/[slug]/scripts/[video-id]-script.md |
| Storyboard |
_docs/videos/courses/[slug]/storyboards/[video-id]-storyboard.md |
| NB2 prompts |
_docs/videos/prompts/[video-id]-prompts.md |
Naming convention: [video-id] = [course]-w[NN]-[type] (e.g., forgotten-ways-w03-opening, mdna-explainer, reframation-w05-social-30s)
Cross-Skill Integration
This skill is designed to work with the other content skills in this project:
/course-author — Use its output as source material. The main teaching, dissonance prompts, and case studies provide the theological substance that videos distill.
/alan-voice — Apply for voice audit on any narration script. Run in audit mode to score the five markers.
/asset-video-prompt — Hand off to this skill when you need AI video model prompts (Runway, Kling, Pika) for specific scenes.
/course-validate — Ensure the video content aligns with the Four Necessities and course structure.
/course-scaffold — Reference for understanding which weeks have which section types and where opening videos fit.
Rules
- 8 weeks, numbered 1-8. No Week 0.
- Every video must serve at least one of the Four Necessities (dissonance, action, reflection, community)
- Scripture woven, not leading — per Alan's voice
- Practice never appears before understanding
- Narration pace: ~145 wpm (cinematic, measured)
- All on-screen text handled in Remotion code — never baked into generated images
- Use brand tokens from
brand-tokens.md — no off-brand colors or fonts
- Use motion vocabulary from
motion-principles.md — no ad-hoc animation descriptions
- Ground everything in Alan's actual published works — never fabricate quotes or frameworks
- Always check for existing content before creating new — build on what's there
1---2name: video-consult3description: Consult on video production for a course — scripture grounding, narrative arc, storyboard, scene structure, and script. Bridges Alan's voice, course theology, and Remotion video production. Use when planning or authoring video content for any course.4user-invocable: true5allowed-tools: Read, Write, Edit, Bash, Grep, Glob6metadata:7 source: https://skillmd.com/skills/joshuashepherd/video-consult8---910Consult on video production: $ARGUMENTS1112$ARGUMENTS should include:13- Course slug or name (e.g., `forgotten-ways`, `reframation`, `mdna`)14- Optionally: specific week or module (e.g., `week 3`, `all weeks`)15- Optionally: video type (opening video, explainer, promo, social cut, course trailer)16- Optionally: specific topic, theme, or scripture passage to ground in17- Empty — ask the user what course and video they're working on1819---2021## Before Starting2223### 1. Understand the Course Context2425Read in this order — stop as soon as you have enough context:26271. Check for existing course content in `content-library/courses/[slug]/` — read any authored weeks for theological themes, arc, and progression282. If this is the Forgotten Ways course, read `/Users/joshuashepherd/Desktop/Dev/repos/forgotten-ways-course/editor/data/course.json` for canonical content293. Read `_docs/COURSE_STRATEGY.md` if it exists — authoritative reference for course structure304. Read `_docs/TRANSFORMATIONAL_COURSE_CHARTER.md` if it exists — the Four Necessities (dissonance, action, reflection, community)3132### 2. Understand the Video System33341. Read `_docs/videos/README.md` — production workflow, project structure, current state352. Read `_docs/videos/style-guide/brand-tokens.md` — colors, typography, motion tokens363. Read `_docs/videos/style-guide/motion-principles.md` — easing, pacing, composition rules374. Read `_docs/videos/templates/script-template.md` — canonical script format385. Read `_docs/videos/templates/storyboard-template.md` — canonical storyboard format396. Check for existing scripts/storyboards in `_docs/videos/courses/[slug]/scripts/` and `storyboards/`4041### 3. Understand the Shared Scene Library4243Read `_docs/videos/courses/_shared/scripts/course-explainer-scenes.md` — the 14-scene explainer library serves as a reference for tone, structure, and visual vocabulary.4445---4647## Consultation Modes4849Determine which mode the user needs. If unclear, ask.5051### Mode A: Full Video Plan (Scripture → Arc → Storyboard → Script)5253For when starting from scratch on a video. This is the primary mode.5455**Step 1 — Theological Grounding**5657Identify the scripture and theological foundations for this video:5859- What is the core concept this video must land? (From the course week's teaching content)60- What scripture passages ground it? (Woven, not proof-texted — per Alan's voice)61- What historical examples illuminate it? (Early church, Chinese underground church, SMRC, Methodist movement)62- What Alan Hirsch frameworks apply? (mDNA, APEST/5Q, Shema, sentness, incarnational-missional)63- What books/chapters are the corpus sources? (Cite as: *The Forgotten Ways* ch3, *5Q* ch7, etc.)6465Output a **Theological Brief** — 200-400 words covering the above. This becomes the foundation everything else builds on.6667**Step 2 — Narrative Arc**6869Design the story structure for this video. Every video — whether 30 seconds or 5 minutes — has an arc.7071For **opening videos** (weekly, ~5 min):72- Hook: name the tension or question the week confronts (15-20s)73- Core concept: plain language, first-person "we" (60-90s)74- Grounding: one scriptural or historical anchor (45-60s)75- Implication: what this means for the learner's life (30-45s)76- Invitation: closing question or anticipation for what's next (15-20s)7778For **explainer videos** (course-level, 2-5 min):79- Use the three-act structure from the shared scene library:80 - Act 1 — What transformation means (composites, tension)81 - Act 2 — Why the current approach fails (data, reality)82 - Act 3 — How formation works (method, the loop)83 - Close — CTA8485For **social cuts / promos** (15s-60s):86- Single tension → single insight → CTA87- Front-load the most compelling 3 seconds (the hook)8889For **module recaps / synthesis** (1-3 min):90- What we explored → what we did → what changed → what's next9192Output an **Arc Document** — a numbered sequence of beats with estimated duration per beat.9394**Step 3 — Scene Breakdown & Storyboard**9596For each beat in the arc, define:9798| Field | Description |99|-------|-------------|100| **Time** | Start–end timecode |101| **Narration** | Exact voiceover text (word count noted) |102| **Alan quote** | On-screen quote from published works, if applicable |103| **Visual** | Detailed visual description — composition, motion, metaphor |104| **On-screen text** | Any titles, labels, callouts |105| **Motion** | Animation/transition description using motion-principles vocabulary |106| **Assets needed** | NB2 backgrounds, illustrations, or code-only elements |107| **Transition out** | How this scene exits to the next |108109Use the storyboard template format from `_docs/videos/templates/storyboard-template.md`.110111**Step 4 — Script**112113Write the full narration script with production notes, using the script template from `_docs/videos/templates/script-template.md`.114115Include:116- Scene-by-scene narration at ~145 wpm (cinematic, not rushed)117- Alan Hirsch quotes — properly attributed to specific books118- Production notes: key concept, corpus references, dissonance moment, call to action119- Asset requirements table120121---122123### Mode B: Scripture & Theology Consult124125For when the user has a video concept but needs help grounding it theologically.1261271. Read the video concept or existing script1282. Identify theological gaps: Where is the Christocentric anchoring? Where is the scriptural grounding? Where are the historical examples?1293. Suggest specific scripture passages, Alan frameworks, and historical parallels1304. Rewrite or annotate sections to strengthen theological depth1315. Apply the alan-voice markers: Christocentric anchoring, pastoral warmth, narrative imagery, theological depth, prophetic intensity132133Output: annotated script or theological brief with specific suggestions.134135---136137### Mode C: Arc & Structure Consult138139For when the user has content but needs help with narrative structure.1401411. Read existing content (script, teaching notes, or course section content)1422. Identify the narrative arc — is there a clear hook → tension → grounding → implication → invitation?1433. Diagnose structural issues: Does it front-load information? Does practice appear before understanding? Does it rush to resolution?1444. Propose a revised arc with beat-by-beat timing1455. Flag pacing issues — are there enough breathing moments? Is the dissonance held long enough?146147Output: revised arc document with structural notes.148149---150151### Mode D: Storyboard & Visual Consult152153For when the user has a script but needs visual direction.1541551. Read the script1562. For each scene, propose visual concepts using the brand vocabulary:157 - Warm charcoal backgrounds, gold accents, organic textures158 - Abstract/silhouette figures, never photorealistic159 - Typography-driven scenes vs. image-driven scenes160 - Motion language from `motion-principles.md`1613. Identify which scenes need AI-generated assets (NB2 backgrounds) vs. code-only animation1624. Write NB2 prompt anchors for any generated assets1635. Note Remotion composition considerations (scene type, transition type, duration in frames)164165Output: storyboard document using the canonical template.166167---168169## Voice Guidelines170171All narration and script content must follow Alan Hirsch's voice. The five markers:1721731. **Christocentric anchoring** (30%) — Jesus is Lord. Every framework points back to Jesus.1742. **Pastoral warmth** (20%) — "We" language. Invitational, not prescriptive.1753. **Narrative imagery** (15%) — Organic metaphors: movement, seeds, fire, rivers. Historical stories.1764. **Theological depth** (10%) — Grounded in Scripture and tradition. Accessible but deep.1775. **Prophetic intensity** (25%) — Reframing questions. Productive dissonance. Calls to risk.178179**Anti-patterns** (never use): corporate consultant tone, detached academic voice, antithesis patterns ("Not X, but Y"), generic motivational language, bullet-point lists as primary content.180181**Rhetorical posture**: Alan speaks from ahead — he describes what the audience doesn't yet see as though it is already visible. He challenges the frame before engaging the question within it.182183**Scripture usage**: Woven, not leading. No sermon-like openings. No proof-texting. Scripture governs the argument but rarely opens it.184185---186187## Output & File Placement188189Save all outputs to the appropriate per-course directory:190191| Output | Save to |192|--------|---------|193| Theological brief | `_docs/videos/courses/[slug]/scripts/[video-id]-theology.md` |194| Arc document | `_docs/videos/courses/[slug]/storyboards/[video-id]-arc.md` |195| Script | `_docs/videos/courses/[slug]/scripts/[video-id]-script.md` |196| Storyboard | `_docs/videos/courses/[slug]/storyboards/[video-id]-storyboard.md` |197| NB2 prompts | `_docs/videos/prompts/[video-id]-prompts.md` |198199**Naming convention**: `[video-id]` = `[course]-w[NN]-[type]` (e.g., `forgotten-ways-w03-opening`, `mdna-explainer`, `reframation-w05-social-30s`)200201---202203## Cross-Skill Integration204205This skill is designed to work with the other content skills in this project:206207- **`/course-author`** — Use its output as source material. The main teaching, dissonance prompts, and case studies provide the theological substance that videos distill.208- **`/alan-voice`** — Apply for voice audit on any narration script. Run in audit mode to score the five markers.209- **`/asset-video-prompt`** — Hand off to this skill when you need AI video model prompts (Runway, Kling, Pika) for specific scenes.210- **`/course-validate`** — Ensure the video content aligns with the Four Necessities and course structure.211- **`/course-scaffold`** — Reference for understanding which weeks have which section types and where opening videos fit.212213---214215## Rules216217- 8 weeks, numbered 1-8. No Week 0.218- Every video must serve at least one of the Four Necessities (dissonance, action, reflection, community)219- Scripture woven, not leading — per Alan's voice220- Practice never appears before understanding221- Narration pace: ~145 wpm (cinematic, measured)222- All on-screen text handled in Remotion code — never baked into generated images223- Use brand tokens from `brand-tokens.md` — no off-brand colors or fonts224- Use motion vocabulary from `motion-principles.md` — no ad-hoc animation descriptions225- Ground everything in Alan's actual published works — never fabricate quotes or frameworks226- Always check for existing content before creating new — build on what's there