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

campaign-brief-and-asset-plan

Turn a campaign goal into a brief the team can build from: the goal said back in one measurable line, the audience and the insight that moves them, the channel mix, the asset list with an owner and a date on each, and the two or three measures you will judge it on.

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

実行スコア 未検証

インストール方法を見る

含まれるファイル(1)

  • SKILL.md2.9 KB

SKILL.md(原文)

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

Campaign brief and asset plan

Use this when someone starts a campaign, names a goal with a date, or hands over notes for one. A dated product release is a different job — that is launch work, and it goes to whoever owns launches.

Say the goal back before you plan anything

One line, specific and measurable, with a deadline on it. Then name, in a short block:

  • The audience, with enough depth to be useful: who they are, what hurts, what they are trying to get done.
  • The channels genuinely in play.
  • The metrics that will be checked afterwards.
  • Who owns the budget.
  • How fast sales follows up on anything the campaign produces.

Anything you were not told is written UNKNOWN, not guessed. Money in particular stays UNKNOWN until the approver fills in the itemized lines.

Write the brief

  • The audience plus the one insight that actually moves them.
  • The message, in two sentences.
  • The channel mix, with one line on what each channel carries. One channel only means a one-channel plan, not a padded mix.
  • The asset list, with an owner and a due date on every row.
  • The launch date.
  • How it gets measured.

Pick two or three measures, and name the headline

Sourced pipeline, the rate at which marketing-qualified leads become sales-qualified ones, cost per opportunity, or plain reach and engagement. Say which one is the headline, because a campaign judged on four numbers is judged on none.

Put dates on it, counting back from launch

Brief lock, asset drafts, approvals, launch, a recurring stakeholder review showing what shipped and what it did, and a retro. The retro runs wins and lessons — at least one of each per person — then cause, fix and prevention on every problem worth solving. Do not overcorrect on noise.

Feed the calendar in the same reply

Show the plan in chat, take one round of edits, then save it and add every asset to the editorial calendar as an idea row in the same reply. A plan whose assets never reach the calendar is a document, not a campaign.

The money gate

Never commit a dollar of paid spend. The plan proposes money; the named approver says yes before anything is bought, and their yes covers that specific line rather than the plan as a whole.

What not to do

Never invent a budget figure, a historical result, or a conversion rate to make the plan look finished. Never put an asset on the list with no owner — an unowned asset is a request, and it gets flagged as one.

レビュー

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

コメント

ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。

まだコメントはありません。最初のコメントを書いてみませんか。

送信するとすぐに公開されます。メールアドレスや電話番号などの個人情報は書かないでください。URL は 2 つまでです。

0 / 1000 文字

このフォームは reCAPTCHA で保護されており、Google のプライバシーポリシーと利用規約が適用されます。

同じリポジトリのスキル

Use when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.

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

Significant-Gravitas/skills-catalog22026年10月22日 更新

Reconcile accounts by comparing GL balances to subledgers, bank statements, or third-party data. Use when performing bank reconciliations, GL-to-subledger recs, intercompany reconciliations, or identifying and categorizing reconciling items.

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

Significant-Gravitas/skills-catalog22026年10月22日 更新

Review open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.

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

Significant-Gravitas/skills-catalog22026年10月22日 更新

Write ad variants that each test one idea, within platform limits and supported claims.

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

Significant-Gravitas/skills-catalog22026年10月22日 更新

Use on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.

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

Significant-Gravitas/skills-catalog22026年10月22日 更新

Use when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.

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

Significant-Gravitas/skills-catalog22026年10月22日 更新

Significant-Gravitas のスキルをすべて見る

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