Who this is for: Product marketers and motion producers preparing an original launch brief.
What to prepare
- A verified sample command and approved output
- The relevant environment and prerequisites
- The specific task the command performs
- Approved product name and access status
Copyable creative brief
An authored planning example. Replace illustrative details with your approved product facts and assets.
Plan a 30-second launch sequence for PRODUCT_NAME using SAMPLE_COMMAND and APPROVED_OUTPUT. Do not execute commands as part of this creative brief. Use only the supplied text and label the sequence as an illustrative demonstration unless actual verified recording is provided. Do not invent package names, flags, credentials or successful results. Open with TASK_DESCRIPTION in plain language. Introduce a readable terminal composition with ENVIRONMENT_NOTE available as supporting context. Reveal the complete command without a long character-by-character typing sequence that delays comprehension. Hold it before showing the supplied output. Highlight the output line that establishes RESULT_BOUNDARY, keeping enough neighboring context to interpret it. If setup, authentication or a separate verification step is required, name it rather than implying the command works in every environment. Introduce the product identity after the task is understandable. End with CURRENT_STATUS and a relevant NEXT_ACTION, such as reading the verified documentation or joining the product's actual waitlist.
Make it your own
- SAMPLE_COMMAND
- Supply exact reviewed syntax; exclude secrets.
- APPROVED_OUTPUT
- Identify whether it is illustrative text or evidence from an actual run.
- ENVIRONMENT_NOTE
- State necessary context without an unsupported universal compatibility claim.
- RESULT_BOUNDARY
- Explain what the shown output establishes and what remains unverified.
- PRODUCT_NAME and TASK_DESCRIPTION
- Use approved identity and a plain-language description of the exact supplied command's job.
- CURRENT_STATUS and NEXT_ACTION
- Supply verified access and a relevant documentation or request destination, with no assumed package availability.
Prepare the technical example
An illustrative developer tool might validate a local configuration file. The brief needs the approved command and a supplied success or error example; the author should not invent a plausible package command.
If the output is simulated for planning, label it clearly. A polished terminal can otherwise imply that a test was actually performed.
Adapt for the viewer
For technical viewers, retain meaningful flags and the relevant output line. For less technical buyers, add a plain-language task statement and explain the result without removing prerequisites.
For a longer version, show one bounded error and correction only when both states are supplied. Do not turn the launch into an undocumented troubleshooting tutorial.
Fix terminal legibility and claims
If the command is too long, reframe the terminal and simplify surrounding decoration rather than deleting meaningful syntax. If the output scrolls past, hold the decisive lines.
Remove fake speed counters and exaggerated execution effects. This prompt describes a developer product launch; it does not claim that Animro provides the tool's API, package or integration.
Review checklist
- Command and output text come from approved material.
- Secrets and private identifiers are absent.
- Illustrative output is distinguished from an executed test.
- Prerequisites and the result boundary remain understandable.