本文へ移動
cccskills
無料GitHub で公開

codexkit-campaign-brief-writer

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.

インストール方法を見る

含まれるファイル(5)

  • SKILL.md5.4 KB
  • agents/openai.yaml169 B
  • examples/common-mistakes.md813 B
  • examples/good-output.md790 B
  • verification/checklist.md1.3 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

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

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Design rigorous A/B test plans with hypothesis, sample size calculation, Minimum Detectable Effect (MDE), randomization strategy, and decision rules. Includes guardrail metrics and rollout playbook. Use when planning product experiments, conversion optimization, or data-driven feature decisions.

日本語の概要は準備中です。原文の説明を表示しています。

hoavdc/CodexKit252026年10月11日 更新

Review REST and GraphQL API designs for consistency, usability, and best practices. Covers naming conventions, versioning strategy, error format, pagination, authentication patterns, and breaking change detection. Use when reviewing API specs, designing new APIs, or auditing existing endpoints.

日本語の概要は準備中です。原文の説明を表示しています。

hoavdc/CodexKit252026年10月11日 更新

Write Architecture Decision Records (ADRs) following the Michael Nygard format. Captures context, options considered, decision rationale, and consequences. Use when making technology choices, framework selections, or any architectural decision that future developers need to understand.

日本語の概要は準備中です。原文の説明を表示しています。

hoavdc/CodexKit252026年10月11日 更新

Assess organizational readiness for financial audits (internal or external). Map assertions to account balances, check evidence completeness, score readiness using a Red/Amber/Green framework, and generate a remediation timeline. Aligned with SOX, IFRS, and GAAP audit standards. Use before scheduled audits or when preparing for first-time compliance.

日本語の概要は準備中です。原文の説明を表示しています。

hoavdc/CodexKit252026年10月11日 更新

Design safe recurring Codex automations with clear prompts, outputs, schedules, and gating rules.

日本語の概要は準備中です。原文の説明を表示しています。

hoavdc/CodexKit252026年10月11日 更新

Refine Product Backlog Items to meet INVEST criteria. Write User Stories with Acceptance Criteria in Given/When/Then format, estimate with Story Points, and flag dependencies. Use before sprint planning when backlog items need grooming. Do not use to prioritize the backlog — that is the Product Owner's decision.

日本語の概要は準備中です。原文の説明を表示しています。

hoavdc/CodexKit252026年10月11日 更新

hoavdc のスキルをすべて見る

このスキルの問題を報告する