# Product Goal Intake

> Define the product, offer, audience, business goal, desired viewer action, proof, and constraints before any marketing video creative work begins.

- Skill: `harsh817/product-goal-intake` (Agent Skill)
- Install (CLI): `npx skillmds@latest add harsh817/product-goal-intake`
- Raw SKILL.md: https://api.skillmd.com/api/skills/harsh817/product-goal-intake/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Marketing & Growth
- Author: harsh817 (https://skillmd.com/u/harsh817)
- Updated: 2026-09-21
- Page: https://skillmd.com/skills/harsh817/product-goal-intake

---


# Product Goal Intake

Use this skill before planning a marketing, explainer, social, product, fashion, styling, or transformation video. The purpose is to understand what the video must achieve commercially or strategically before creative direction, storyboard, generation, or editing begins.

## Outcome

Produce a concise product/goal intake packet that can be placed into `G0 Product / Goal Intake` in `PRODUCTION_GATES.md`.

The packet should make these decisions clear:

- What product, service, offer, brand, creator, or concept the video is for.
- Who the target viewer is.
- What the viewer should believe after watching.
- What action the viewer should take.
- What business goal the video serves.
- What proof makes the message believable.
- What emotion the video should create.
- What constraints, claims, brand rules, or visual risks matter.

## Required Questions

When the information is missing and cannot be safely inferred, ask only the smallest useful set of questions. Prefer these:

- What is the product or offer behind this video?
- Who exactly should watch this?
- What should the viewer do after watching?
- What proof do we have or need to show?

Do not ask every question if the answer is already available from the user's materials.

## Intake Packet

Write the result in this shape:

- Product / offer:
- Target viewer:
- Viewer problem:
- Desired belief shift:
- Desired action:
- Business goal:
- Core proof:
- Emotional direction:
- Mandatory inclusions:
- Must avoid:
- Gate decision:

Use `approved` only when enough context exists to brief the creative director. Use `pending` when user confirmation is needed. Use `needs-fix` when the product/goal is contradictory, unclear, or impossible to support with the available proof.

## Decision Rules

- A script is not a product goal. Treat it as creative material until the product, audience, and desired action are clear.
- A reference video is not a strategy. Extract useful style or structure later, but first define what the current video is selling, proving, or teaching.
- If the product is unknown, do not generate visuals yet.
- If the goal is awareness, trust, lead capture, direct sale, education, or demo, say so explicitly because it changes the creative direction.
- If no call to action is provided, propose a soft default and mark the gate `pending` for user approval.

## Handoff

After `G0 Product / Goal Intake` is approved or waived:

- Hand the product, audience, belief shift, proof, emotion, and CTA to `marketing-creative-director`.
- Keep style references separate for `editing-style-director`.
- Keep production constraints visible in `production-quality-gates`.