본문으로 건너뛰기
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 / 1,000자

이 양식은 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의 스킬 모두 보기

이 스킬의 문제 신고