PRODUCTIVITY

Marketing campaign planning and operations

Convert a campaign goal into channel messaging, an asset plan, approval gates, and measurement design.

PROMPT
Role: a precise operations analyst

Objective: Build an execution-ready campaign plan with traceable claims, channel adaptations, QA, and human approval before publishing or spend.

Inputs:
- Campaign brief: {{campaign_brief}}
- Audience: {{audience}}
- Value proposition and offer: {{offer}}
- Channels: {{channels}}
- Business goal and decision: {{business_goal}}

Workflow:
1. Convert the goal, audience, offer, and channels into a one-sentence campaign contract with success and failure metrics.
2. Derive audience problems, awareness stage, objections, and desired action from evidence.
3. Define one governing message and proof points, then adapt format, tone, and call to action by channel.
4. Build an asset matrix with owner, input, specification, deadline, dependency, approver, and reusable elements.
5. Design fact, brand, accessibility, privacy, platform-policy, and pre-publish approval gates.
6. Define channel metrics, experiment hypotheses, minimum sample, and stopping rules; never publish or spend automatically.

Output format:
## Campaign contract and metrics
## Audience insight and evidence
## Governing message and proof
## Channel execution matrix
## Asset owners and deadlines
## QA and approval gates
## Measurement and experiments

Quality rules:
Use only supplied material and verifiable facts. When information is missing, do not guess: state the gap, any necessary assumption, and its effect on the result. Before concluding, check every constraint and required output field.

Negative prompt

Unsupported facts, fabricated citations, vague conclusions, missing constraints, unverified claims, and unrequested scope expansion

Workflow

  1. Fill variables with concrete facts, scope, actors, and desired outcomes rather than abstract adjectives.
  2. Check the assembled prompt for conflicting conditions, then paste it into a compatible tool.
  3. Treat the first answer as a draft and refine one failed condition at a time.

Verification

  • Confirm every goal, constraint, and output field is present.
  • Check figures, dates, quotations, and code against primary sources and real tests.
  • Keep a human responsible for evidence, feasibility, and final approval.