create-feature-launch-video

name	create-feature-launch-video
description	create a feature launch video from a feature brief, proof points, motion graphics, captions, and export variants.

create-feature-launch-video

Purpose

Create a feature launch video from a feature brief, proof points, motion graphics, captions, and export variants.

Implementation status: new scaffold. No complete existing implementation was found; use this as a structured starting point and mark runs as blocked until provider details, credentials, or scripts are added.

Sources: none.

Extraction notes: Composes atoms from source workflow: none.

Inputs

• A clear user brief or source asset path.
• Brand, product, audience, platform, and approval constraints when relevant.
• Required credentials or provider access for any external service used by this skill.
• Output directory or test-run directory where artifacts should be saved.

Composed Atoms

• generate-ad-concepts
• create-storyboard
• create-motion-graphics-hyperframes
• add-captions-klap
• export-video-final

Workflow

1. Read the brief and confirm all required inputs are present.
2. Load any referenced files in this skill folder only when they are needed.
3. Because this is a scaffold, build a dry-run payload or written plan and clearly mark missing implementation details.
4. Save outputs under the requested output folder or skills/test-runs/<timestamp>/<skill-name>/ during tests.
5. Write or update a manifest.json for executable runs with status, provider, outputs, warnings, and errors.

Decision Rules

• Prefer extracted atoms over recreating provider-specific details in this molecule.
• If an atom is marked as a scaffold, stop before production execution and report what is missing.
• Keep human approval gates when the source workflow requires brand, visual, or final-video review.
• Do not skip review and verifier steps before delivery.

Output

• Primary artifact or written plan requested by the skill.
• manifest.json for executable runs.
• verification.md or a short verification summary that names the checks performed.
• Any generated source assets, intermediate files, or final exports in the run folder.

Quality Checks

• Required files exist and paths in the manifest are valid.
• Output matches the requested format, platform, duration, dimensions, or text structure.
• Brand claims, captions, on-screen text, and CTAs follow the provided brand rules.
• Provider failures, skipped integrations, and human-review needs are explicit.

Failure Modes

• Missing credentials, provider access, or source files.
• Output does not match requested dimensions, duration, structure, or brand constraints.
• Generated media contains artifacts, unreadable text, unsafe claims, or caption collisions.
• Scaffolded skills cannot run production workflows until implementation details are added.