Marketing: Turn Campaign Requirements into an Execution Brief

Fictional brand: Muyuan Stationery Campaign: new notebook launch; period: October 1 to 7 Channels: brand official account and email; claims: can lie flat for writing, 80 pages Budget, discounts, and performance data are not provided; fabricating sales or user reviews is not allowed.

Preset Campaign Brief Goal: Introduce new product features; specific performance goals are pending confirmation by the person in charge. Content direction: Show lie-flat writing scenarios, inner page structure, and daily note-taking uses. Draft headline: Spread Out Your Inspiration to Write — Muyuan 80-Page Notebook. Deliverables: official account article draft, email copy draft, asset requirements checklist. Pending approval: product claim evidence, budget, launch schedule, and image authorization. No discounts, sales, or customer testimonials were written; nothing was published or mass-sent.

Applicable Scenarios

Organize audiences, goals, assets, and delivery milestones, and generate channel copy directions and items pending approval.

This demo uses fictional business data and pre-prepared outputs to demonstrate a customizable workflow; it is not a customer case study, real-time AI execution, or actual business result.

Work Steps

Extract verified product facts and channel requirements.
Generate the brief structure, copy directions, and asset checklist.
Check unverified marketing claims and approval items one by one.

Human Review and Boundaries

The brand owner confirms product facts, asset authorization, and channel strategy before publishing; email audiences and sending permissions are reviewed separately.

Customizable Content

Customize brand tone, channel templates, and content review checklists, and organize approved materials into a team Skill.

How to Validate

Test separately with normal inputs, missing fields, and conflicting materials; check that key fields can be traced back to the input, missing content is clearly marked, and numerical calculations are completed by reviewable rules. The samples and delivery scope agreed by both parties shall prevail.

Platform and Delivery

Instructions, templates, supporting scripts, and review steps can be customized for Codex or Claude. Specific product versions, tool permissions, and system interfaces are confirmed during the requirements phase and tested separately. Deliverable source files, test samples, and usage documentation; this page does not connect to external systems, send notifications, or perform business operations.

Input

Output