# Presentation Storyboard

> Presentation Storyboard

- Skill: `lunasoft2001/presentation-storyboard` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add lunasoft2001/presentation-storyboard`
- Raw SKILL.md: https://api.skillmd.com/api/skills/lunasoft2001/presentation-storyboard/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: lunasoft2001 (https://skillmd.com/u/lunasoft2001)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/lunasoft2001/presentation-storyboard

---


# Presentation Storyboard

Build a slide-by-slide narrative structure before any visual is created. Output is a storyboard document that feeds `presentation-pptx-builder` and `presentation-speaker-notes`.

## Required Inputs

Collect the following before generating. Use `vscode_askQuestions` if any are missing:

| Field | Required | Description |
|-------|----------|-------------|
| `topic` | ✅ | Presentation subject |
| `audience` | ✅ | Who attends and their context |
| `duration` | ✅ | Total length in minutes |
| `key_messages` | Recommended | Up to 5 core takeaways |
| `style` | Optional | Tone: corporate / storytelling / educational / pitch |
| `language` | Optional | Output language (default: user's language) |

## Storyboard Generation Rules

1. **Calculate slide budget**: use ~2 minutes per content slide, 1 minute for title/closing.
2. **Apply a 3-act narrative arc**:
   - **Act 1 — Context** (≈20% of slides): Why this matters / the problem
   - **Act 2 — Content** (≈60% of slides): Data, analysis, solutions, story
   - **Act 3 — Action** (≈20% of slides): Recommendations, next steps, Q&A
3. **One message per slide**: each slide has exactly one main message (the slide's headline).
4. **No filler slides**: every slide must earn its place. Combine or cut if needed.

## Per-Slide Output Format

For each slide, produce:

```
### Slide <N>: <Title>

**Act**: Context / Content / Action
**Message**: One sentence — the single takeaway from this slide.
**Objective**: What the audience should feel or understand after this slide.
**Duration**: ~X min
**Visual suggestion**: [chart type / photo / diagram / table / text-only] — brief description
**Transition note**: How this slide connects to the next (one sentence).
```

## Full Storyboard Document Format

```markdown
# Storyboard: <topic>

**Audience**: <audience>
**Total duration**: <N> min
**Slide count**: <N>
**Key messages**:
- <message 1>
- ...

---

## Act 1 — Context (<N> slides)

[slides...]

## Act 2 — Content (<N> slides)

[slides...]

## Act 3 — Action (<N> slides)

[slides...]

---

## Narrative Thread Summary

One paragraph explaining the red thread that connects all slides.
```

## Output

Always produce **two output files** — both are required for the pipeline to work end-to-end:

1. **`/deliverables/<slug>/storyboard.docx`** — human-readable document (use the `docx` skill if available; otherwise produce Markdown for the user to convert).
2. **`/deliverables/<slug>/storyboard.json`** — machine-readable JSON consumed by `presentation-pptx-builder` in Stage 2.

### storyboard.json Schema

Emit this JSON alongside the docx, serializing every slide from the storyboard:

```json
{
  "title": "<topic>",
  "slug": "<slug>",
  "theme": "corporate",
  "slides": [
    {
      "number": 1,
      "title": "<Slide Title>",
      "message": "<One-sentence key message>",
      "act": "Title | Context | Content | Action | Section break",
      "duration_min": 2,
      "visual_type": "title | text | chart | diagram | photo | two-column | section | blank",
      "body_bullets": ["Optional bullet 1", "Optional bullet 2"]
    }
  ]
}
```

**Rules for `visual_type`:**
- Use `"title"` only for slide 1.
- Use `"chart"` when the visual suggestion from the storyboard is any type of data chart.
- Use `"diagram"` for flows, processes, org charts, timelines.
- Use `"photo"` for image-first slides.
- Use `"text"` for bullet-point slides with no chart or diagram.
- Use `"section"` for act-break slides.

Save the JSON to `/deliverables/<slug>/storyboard.json` before or alongside the docx. This file is the direct input to `presentation-pptx-builder`'s `--storyboard` argument.

## Quality Rules

- Every `key_message` must appear as a slide headline in Act 2 or Act 3.
- No slide should carry more than one concept.
- Visual suggestions must match the data type (never suggest a bar chart for a qualitative claim).
- If `duration` is under 5 min, limit to 4 slides max (title, problem, solution, call-to-action).
- If `duration` is over 45 min, recommend splitting into two modules.

## Limitations

- Does not generate actual images or graphics — only text descriptions.
- Does not produce the PPTX file — hand off to `presentation-pptx-builder`.
- See `references/slide-structure-guide.md` for narrative models and visual suggestion catalog.