Product screenshots to a directed promo video

Use video-shotcraft for shot direction and the official Remotion skills for implementation discipline, then verify the rendered file.

The path and every handoff

1. 1
   Direct the sequence video-shotcraft

   FUNCTION VERIFIED

   Turn the product story into deliberate shots, timing, transitions, and a still ending rather than an undirected animation.

   Input

   Product screenshots, product promise, duration, and aspect ratio

   Instruction

   Follow video-shotcraft's required template-versus-free-form choice, then write a frame-addressed shot plan before implementation.

   Output

   shot-plan.md human confirmation

2. 2
   Implement in Remotion remotion skills (official, 10-skill pack)

   FUNCTION VERIFIED

   Translate the approved shot plan into a technically correct, editable Remotion composition.

   Input

   shot-plan.md and normalized product assets

   Instruction

   Use the official timing, animation, asset, and project-structure rules while preserving the shot plan's visual direction.

   Output

   remotion-project/

3. 3
   Render and verify Verification or human checkpoint

   UNVERIFIED

   Prove that the deliverable exists and meets its mechanical contract before subjective review.

   Input

   remotion-project/

   Instruction

   Render with a pinned browser executable, then inspect codec, duration, resolution, frame rate, file size, and playback.

   Output

   promo.mp4 and verification.json human confirmation

Result you can inspect now

EVIDENCE REPLAY Same five-second brief rendered with video-shotcraft and Remotion official skills

2026-07-25

What this proves: Both skill methodologies produced a working 150-frame Remotion scene from the same fixed brief. Setup, render timings, failures, output bytes, and frame 75 were recorded.

What it does not prove: A user-supplied screenshot-to-video workflow, repeat-run success rate, public MP4 download, audio, or a fifteen-second final promo.

• video-shotcraft: 13.8s render for 150 frames
• Remotion official skills: 13.5s render for 150 frames
• Both routes required a local chrome-headless-shell in the constrained environment

Open the full source record →

Known limits

• The published comparison used a fixed typography-and-check brief, not user screenshots.
• Only still frames are currently public; the final MP4 is not yet downloadable.
• Repeat-run workflow success has not been measured.
• Headless environments may need a local chrome-headless-shell and concurrency set to one.

Implementation pack

The pack is generated from this path record and the tested-skill source data. Install commands, commits, evidence status, handoffs, and limitations stay attached to the plan.