Installs into .claude/skills of the current project.
Are you the author of Video Planning?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/sanidhya14321-video-planning)
---
name: video-planning
description: "Develop technical video briefs, accurate scripts, storyboards, and reference-video breakdowns before production."
---
# Video Planning
Define one viewer, one promise, and one visible payoff. Ground factual claims in supplied evidence or current primary sources. A saved viral reference is evidence of an editing pattern, not proof of its claims.
For a reel or an abstract/fast request, use [reel direction](../video-forge/references/reels.md) to select a visual argument, semantic moving objects, beat accents, proof holds, and a payoff. State the intended transformation per shot; do not use labels alone as the storyboard.
Read [planning workflows](references/workflows.md). Write a brief and a scene table with duration, copy, visual evidence, narration, and asset needs. Respect the user's chosen format and existing approved copy. Translate the scene table into the [project contract](../../docs/project-format.md).
For reference analysis, record observable shot timing, framing, typography, and sound separately from inferred intent. Sample frames and listen before claiming to understand a recording. The CLI does not download or analyze YouTube videos automatically.
For an executable job, use the director and relevant production module. Never invent benchmark results, product features, quotations, or word timestamps to make a story fit.
