Project Tool Launch Video

1つのタスクを、混乱から完了まで、60〜90秒で。

AIをプロジェクト管理・課題追跡ツール向けのローンチ動画ディレクターに変え、1つのタスクを受信箱から完了まで追う60〜90秒のフィルムの脚本と絵コンテを作ります。ツールが機能することを、見せることで証明します。

こんな方におすすめ

他者の仕事を整理するツールをローンチするプロダクトチームの方

所要時間

初稿まで~60分

レベル

中級

3ステップでインストール

登録不要。CLIツールも不要です。お使いのAIを選んで、1行コピーして貼るだけです。

Pro — 全511件のスキル

ご自分で入れたい場合は、スキルを購入（$4.99）し、購入完了画面からZIPをダウンロードして、上のディレクトリに展開し、AIのセッションを再起動してください。結果は同じです。すでに購入済みの場合は、AIアシスタントにダウンロードしてもらうこともできます。

パックの内容

SKILL.md（手順書）1点とスターターテンプレート1点が入っています。プレビューはこちらです：

Project Tool Launch Video

When to use

You are launching a project-management, issue-tracking, or task-planning tool and screenshots alone don't explain why it's better
Your launch page has a demo video slot and the current video is a feature tour nobody finishes
You need a video that works muted in a feed — captions carry it, visuals prove it
You are announcing a major version, a redesign, or a new workflow (e.g. triage, sprints, roadmaps) inside an existing tool
You need one film that works on the landing page, in a launch post, and as a conference-loop clip

Workflow

Pick the one task (input: your tool → output: a single hero task)
Choose one realistic task that exercises the tool's core loop: it arrives messy (a vague request in an inbox or form), gets clarified, gets assigned, moves across the board, and ends done with something visible to show for it. The task must be specific — "Fix the checkout bug that blocks gift cards" beats "Manage your projects." If your tool has three core loops, pick the one a new user hits first; the other two get their own videos later. Everything in the film serves this one task's journey.
Script the journey in beats (input: hero task → output: 60–90s script)
Structure the film as five beats, each 10–20 seconds: 1) The mess — the task arrives as chaos (a rambling message, a scattered thread). 2) Capture — one click turns it into a tracked task, fields filled, owner assigned. 3) Work — the task moves: a comment resolves a question, a subtask splits off, status changes. 4) Done — the task lands in Done and the visible result appears (the fix shipped, the page live, the client notified). 5) The line — one sentence on what the tool is for, plus the call to action. Write narration as short spoken lines (under 12 words each) and burn captions into every frame — the film must make sense with the sound off.
Storyboard with real UI (input: script → output: shot-by-shot board)
Storyboard every beat with real screen recordings of your actual product — no mockups, no animations pretending to be the UI. Each shot lists: what's on screen, what moves, the caption line, and the duration. Rule: every claim on screen must be a real action in the product (a real status change, a real comment, a real filter). If a shot needs a fake click to look good, cut the shot — a launch video that fakes the product poisons the first trial. Keep the cursor calm and the pace human; frantic cursor-jumping reads as hiding something.
Cut for the muted feed (input: rough cut → output: feed-ready cut)
Edit to a strict rhythm: no shot longer than 4 seconds, no dead air, captions always on screen, the task's title visible in every shot so a viewer who joins mid-film knows what they're watching. Test the cut muted on a phone: if you can't follow the task's journey with no sound, the captions or the shot order are failing — fix those, not the music. Music, if any, sits low under the captions and stops entirely for the final line.
Export three versions (input: final cut → output: landing, feed, loop versions)
Export: a) Landing (16:9, with sound, ends on the CTA button), b) Feed (square or vertical, captions burned in, autoplays muted, ends on the product name + one-line promise), c) Loop (no beginning or end — the Done state flows back into a new task arriving, for conference screens and expo booths). Each version gets a thumbnail taken from the Done beat — the moment of payoff, not the logo. Publish with the same one-line description everywhere: what the tool does, for whom, in one sentence.

テンプレートのプレビュー

Project Tool Launch Video — Template

60–90 seconds. One hero task, from mess to done. Captions on every frame.

The hero task

Task title (visible in every shot): {e.g. "Fix the checkout bug that blocks gift cards"} Arrives as: {rambling message / form / thread — quote it} Ends as: {visible result — fix shipped / page live / client notified} Core loop shown: {capture → assign → work → done}