build-product-demo

Build Product Demo

Turn verified product behavior into a compact proof story. Treat the final media as an executable claim about the product, not as a decorated feature list.

Choose the mode

• Plan: inspect the product and produce the brief, evidence inventory, feature coverage, director treatment, script, and beat plan.
• Produce: complete the plan, create deterministic setup and capture tooling, record, edit, and verify the final media.
• Diagnose: inspect an existing demo, identify the first broken layer, and revise the smallest responsible artifact. Check truth, story, visible state change, attention, narration/action alignment, capture, then encoding.

If the user asks to “make” or “finish” the demo, default to Produce. Do not stop at a script while safe, in-scope production work remains.

Establish the boundary

1. Resolve the exact product repository, revision, runtime, audience, channel, target duration, aspect ratio, language, available assets, and publishing scope. Inspect before guessing.

2. Read repository instructions and existing demos, screenshots, tests, fixtures, launch scripts, and marketing claims. Search before adding a new recorder or seed path.

3. Separate immutable product facts, creative choices, and missing production facts. Do not turn an unknown into a visual claim.

4. Select one reference benchmark: the user's strongest previous demo, a product-native launch video, or a clearly named quality bar. Record what to preserve and what to avoid. Do not rely on generic taste words.

5. Choose one audience doubt and one proof proposition. Complete:

   The audience doubts whether [product claim]. The demo proves [outcome] by showing [observable change].

6. Define the opening and landing state. Reject a concept whose product or audience state is materially unchanged at the end.

Read directing.md before selecting features or writing beats. Read production.md before recording, generating narration, or using deterministic fixtures.