Boring video

Orchestrate content development and a progressively refined HyperFrames project as one chain. Content is established before it is adapted for speech or visuals; scene direction establishes rendered visual evidence, storyboard plans buildable frames, and HyperFrames owns production and playable review.

Intake

Resolve existing decisions from the request and project files. First classify the input:

• Content-driven: research, evaluation, analysis, opinion, tutorial, news, profile, or another narrated work whose value depends on a complete argument and may also become a blog article.
• Direct-production: a locked script, product promo, UI demonstration, music-led piece, short motion graphic, or another work that does not need an article to establish its meaning.

Resolve reusable production defaults from explicit project, series, brand, or team guidance before asking for one-off choices. Create the workflow BRIEF.md at intake and record each adopted default, its source, and its scope there so every upstream skill can read it before making content or voice decisions; carry the same brief into the HyperFrames project when that project is created. A current request overrides a reusable default. Defaults may cover recurring structure, language and voice, design truth, cover ratios, publishing targets, or terminal presentation, but must not be inferred from an unavailable personal profile. Keep project-specific conventions in project files rather than universalizing them into this skill.

For content-driven work, locate the first missing approved content artifact. A supplied article counts only when the user explicitly confirms it as the content master. Store or adapt it as content/ARTICLE.md with this provenance: