video-script

这段内容是审核时保存的快照。外部来源才是完整且最新的版本。

---
name: video-script
description: Use when the user wants to write a video script for a product demo, feature walkthrough, launch video, or social media video about a feature or product change
---

# Video Script Writer

Write video scripts for product demos, feature walkthroughs, and launch videos. Handles pacing, visual directions, timing, and platform-appropriate lengths.

## Input Resolution

Resolve the argument (if provided) in this order:

1. Path to an existing marketing brief (`.md` containing "Executive Summary" or "Key Messages") -> **marketing brief**
2. Path to an existing blog post (`.md` with blog post structure) -> **blog post**
3. Path to an existing changelog -> **changelog**
4. Path to an existing newsletter -> **newsletter**
5. Matches GitHub URL or `#\d+` pattern -> **PR**
6. Contains `...` or `..` -> **git ref range**
7. Resolves to existing file/directory -> **codebase feature**
8. Otherwise -> **freeform text**

If no argument is provided, ask: "What should the video be about? You can provide a marketing brief, blog post, changelog, PR URL/number, git ref range, file/directory path, or just describe the feature."

If multiple interpretations match, confirm with the user.

## Process Flow

```dot
digraph video_script {
    rankdir=TB;
    "Resolve input" [shape=box];
    "Phase 1: Discovery" [shape=box];
    "Phase 2: Configure" [shape=box];
    "Phase 3: Outline" [shape=box];
    "Outline approved?" [shape=diamond];
    "Phase 4: Write" [shape=box];
    "Phase 5: Review" [shape=box];
    "Approved?" [shape=diamond];
    "Phase 6: Output" [shape=box];

    "Resolve input" -> "Phase 1: Discovery";
    "Phase 1: Discovery" -> "Phase 2: Configure";
    "Phase 2: Configure" -> "Phase 3: Outline";
    "Phase 3: Outline" -> "Outline approved?";
    "Outline approved?" -> "Phase 3: Outline" [label="no, revise"];
    "Outline approved?" -> "Phase 4: Write" [label="yes"];
    "Phase 4: Write" -> "Phase 5: Review";
    "Phase 5: Review" -> "Approved?";
    "Approved?" -> "Phase 4: Write" [label="revisions"];
    "Approved?" -> "Phase 6: Output" [label="yes"];
}
```

**Do NOT skip phases.** Ask questions at a natural pace. If the user answers multiple at once, accept bundled answers and skip ahead.

If the user says "just pick defaults" or similar, pick reasonable defaults, state what you chose, and ask for a single confirmation.

## Phase 1: Discovery

### Step 1 - Analyze the input

| Input type | What to read |
|---|---|
| Marketing brief | Extract problem statement, value prop, audience, key messages. Skip to Step 3. Still do Step 2 if brief lacks product context. |
| Blog post | Extract headline, key points, audience, CTA. Skip to Step 3. |
| Changelog | Extract key entries, focus on the most impactful changes. Skip to Step 3. |
| Newsletter | Extract subject, key updates, CTA. Skip to Step 3. |
| PR | Diff, PR description, review comments, commit messages. For large PRs (20+ files), focus on user-facing changes. |
| Git refs | `git diff` and `git log` between refs. Prioritize user-facing changes. |
| Codebase feature | Read the specified files/directories. |
| Freeform text | Parse the user's description. If it lacks specifics, ask the user to provide more detail or point to a specific file/PR. |

**User-facing changes** include: new features, UI changes, API changes, performance improvements, bug fixes, and documentation updates. **Internal changes** include: refactors, test additions, CI changes, and dependency bumps.

**Error handling:**
- `gh` not available -> inform user, offer alternative input
- Invalid PR/ref -> ask user to verify
- File not found -> ask for correct path

### Step 2 - Read broader product context

Read if they exist: README, docs/, package.json (or equivalent).

If nothing found, ask: "Can you briefly describe the product and who it's for?"

### Step 3 - Present understanding

> "Here's what I'll base the video script on:"
>
> - Feature A - short description
> - Feature B - short de