Skip to content

hoavdc/CodexKit / skills/codexkit-campaign-brief-writer

codexkit-campaign-brief-writer

Unverified

Write agency-standard creative briefs for marketing campaigns. Structure Background, Objective (SMART), Target Audience persona, Key Message, Mandatories, KPIs, Timeline, and Budget Allocation. Use when briefing agencies, creative teams, or internal marketing on a new campaign.

Campaign Brief Writer

When to Use

  • When launching a new marketing campaign (digital, ATL, BTL, or integrated)
  • When briefing an external agency or freelance creative
  • When internal marketing teams need a structured campaign kickoff
  • When aligning stakeholders on campaign scope before execution

Procedure

Step 1 — Background & Context

  1. Business context: Why this campaign now?
  2. Product/service being promoted
  3. Market situation and competitive context
  4. Previous campaign results (if applicable)

Step 2 — SMART Objective

  • Specific: What exactly do we want to achieve?
  • Measurable: What metric defines success?
  • Achievable: Is it realistic given budget and timeline?
  • Relevant: How does it serve business goals?
  • Time-bound: When must it be achieved?

Step 3 — Target Audience

Build a mini-persona:

  • Demographics and psychographics
  • Pain points and motivations
  • Where they consume content
  • Current perception of our brand
  • Desired perception after campaign

Step 4 — Key Message

  1. Single-minded proposition (one sentence)
  2. Supporting proof points (3 max)
  3. Tone of voice guidelines
  4. Brand personality traits to convey

Step 5 — Mandatories & Constraints

  • Brand guidelines (logo, colors, fonts)
  • Legal/regulatory requirements
  • Do's and don'ts
  • Channels and formats required

Step 6 — KPIs & Measurement

KPITargetMeasurement Tool
ImpressionsXPlatform analytics
CTRX%Google Analytics
ConversionsXCRM/attribution
Brand liftX%Survey

Step 7 — Timeline & Budget

PhaseDatesBudget
Creative development
Production
Media buy
Launch
Optimization
Reporting

Inputs

InputRequiredFormat
Product/serviceYesDescription
Campaign objectiveYesSMART format
Target audienceYesPersona or description
Budget rangeRecommendedCurrency amount
TimelineYesStart and end dates

Output

## Campaign Brief — [Campaign Name]

### Background
[Business context and why now]

### Objective
Increase trial signups by 30% within Q3 through a targeted digital campaign
across LinkedIn and Google Ads, supporting the company's annual growth target.

### Target Audience
| Attribute | Detail |
|-----------|--------|
| Role | VP/Director of Engineering |
| Company size | 50–500 employees |
| Pain point | Scaling development velocity |
| Content habits | LinkedIn, Hacker News, podcasts |

### Key Message
**"Ship 2x faster without hiring 2x"**
- Proof 1: 40% reduction in CI/CD time
- Proof 2: Used by 500+ engineering teams
- Proof 3: SOC 2 compliant from day one

### Tone: Confident, technical, peer-to-peer (not salesy)

### Mandatories
- Use updated brand guidelines v3.0
- Include legal disclaimer for trial terms
- All assets in English, preview in dark mode

### KPIs
| KPI | Target |
|-----|--------|
| Trial signups | 3,000 |
| CPL | < $25 |
| CTR | > 1.5% |

### Timeline & Budget
| Phase | Dates | Budget |
|-------|-------|--------|
| Creative | Apr 1–15 | $5,000 |
| Production | Apr 15–22 | $3,000 |
| Media | Apr 22 – Jun 30 | $40,000 |
| Total | | $48,000 |

Definition of Done

  • Background and business context provided
  • SMART objective defined
  • Target audience persona complete
  • Key message with proof points
  • KPIs with measurable targets
  • Timeline and budget allocation
  • Mandatories and constraints listed

Examples

Prompt

Write a campaign brief for launching our new AI code review tool.
Target: Engineering leaders at mid-market companies.
Budget: $50K. Timeline: Q2. Goal: 3,000 free trial signups.
Channels: LinkedIn, Google Search, Dev podcasts.

Quality Criteria

  • All placeholder sections are filled with domain-specific content
  • Structure follows the relevant industry standard or framework
  • Language matches target audience (technical / executive / legal)
  • Output is ready for review — not a rough draft requiring major rework

Verification (4C)

CheckQuestion
CorrectnessDoes the draft structure follow the stated framework or industry standard?
CompletenessAre all required sections present with substantive (not placeholder) content?
Context-fitDoes tone, detail level, and terminology match the intended audience?
ConsequenceIf sent to the intended recipient without further editing, what would fail?

Edge Cases

  • No existing template for this type — Use the closest available template and document all customizations made.
  • Stakeholder requirements conflict — Flag conflicts explicitly in the draft. Do not silently choose one requirement over another.
  • Output required in multiple formats — Produce the canonical format first, then derive others. Note any formatting limitations.

Changelog

  • v1.0.0 — Initial release
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 464kUpdated Claude CodeCodexVerifiedInstall
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 464kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 318kUpdated Claude CodeCodexUnverifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 318kUpdated Claude CodeCodexUnverifiedInstall