Plotloom Episode Card

Plotloom Episode Card

When to Use

Use when series.md and characters.md exist but the next episode needs a compact intent anchor before writing video prompts. This skill is for intent, not full script/storyboard generation.

Inputs

• series.md
• characters.md
• Optional existing episodes/epXXX/episode-card.md
• User direction for episode number, runtime, hook, conflict, reversal, or ending handoff.

Outputs

• episodes/epXXX/episode-card.md

Read These Resources When...

• Read references/episode-intent.md when the hook, visible conflict, reversal, or ending handoff is weak.
• Use templates/episode-card.md for output shape.

Workflow

1. Read series.md and characters.md. 2. If series/character context is missing, hand off to plotloom-series-brainstorming rather than inventing it. 3. Create or update only episodes/epXXX/episode-card.md when story intent needs anchoring. 4. Keep the card lean: runtime target, opening hook, emotional hook, main conflict, escalation, reversal, ending hook, required characters/assets, locations, and continuity constraints. 5. Hand off to plotloom-shot-prompts.

Episode Card Rules

• The first 1-3 seconds need a visible hook, not pure exposition.
• The main conflict must be filmable as action, posture, expression, prop, or dialogue window.
• Include a reversal/reveal and an ending handoff for the next clip or episode.
• Do not create mandatory script.md, storyboard.md, review.md, or director-brief.md.
• If a full script/storyboard is requested, mark it outside MVP and ask for explicit direction before expanding scope.

Stop Conditions

Stop after the episode card is clear. Do not call image/video tools, write video prompts, or select media.

Next Skill Handoff

Use plotloom-shot-prompts to turn this card into continuous video prompt tasks.

Failure Modes

• Missing series.md or characters.md: hand off to plotloom-series-brainstorming first.
• Episode already has a good card: summarize it and proceed to prompt generation.
• User asks for full script/storyboard: confirm scope; do not create mandatory heavyweight artifacts by default.

Episode Intent Reference

Short-Drama Episode Anatomy

• 0-3s hook: visible pressure, humiliation, threat, or mystery.
• Setup: who wants what in this episode.
• Escalation: power imbalance becomes sharper.
• Reversal/reveal: identity, leverage, private phrase, evidence, or unexpected ally changes the scene.
• Ending hook: final frame creates the next clip/episode question.

Strong Hooks

• A character is publicly underestimated.
• A prop or phrase reveals hidden identity.
• A villain makes a visible mistake.
• A quiet character refuses the expected status role.

Weak Hooks

• Pure exposition.
• Long backstory voiceover before any visible conflict.
• A generic argument with no series-specific pressure.

Episode Card Is Not a Script

The episode card anchors intent. It should not become mandatory script.md, storyboard.md, or director brief. If the user needs those artifacts, ask before expanding scope.

Preserve the Series Engine

Every episode should exercise the recurring conflict engine while adding one concrete change: new evidence, new ally/enemy, new cost, or new public reversal.

Episode {{episode_number}} Card

Metadata

• Episode id: ep{{episode_number}}
• Episode title:
• Runtime target:
• Source series engine:

Logline

Opening Hook

What must be visible in the first 1-3 seconds.

Emotional Hook

Main Conflict

Filmable conflict, not abstract backstory.

Escalation

Reversal / Reveal

Ending Hook / Handoff

The final state another clip or episode can continue from.

Required Characters / Assets

• Character:
• Required reference path:
• Prop / scene:

Locations

Continuity Constraints

• Character invariants:
• Wardrobe/prop continuity:
• Previous/next clip handoff:

Notes for Video Prompts

Open Questions