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

marketing-planning

Builds the marketing plan of record — objectives, channel mix, budget allocation, sequencing, and the measurement that says whether it worked. Use this for annual or quarterly planning, when budget must be allocated or defended, when marketing activity feels busy but undirected, or when a plan needs pressure-testing before commitment.

インストール方法を見る

含まれるファイル(2)

  • SKILL.md2.6 KB
  • references/sources.md1004 B

SKILL.md(原文)

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

Marketing planning

Start from the constraint, not the calendar

Name the single thing limiting growth right now: not enough people know, not enough of the right people know, they know but do not believe, they believe but do not act, or they act but do not stay. Each implies a different plan. A plan that funds all five funds none properly.

Structure

  1. Objective — one primary number with a date. Supporting metrics are supporting.
  2. The constraint and the evidence for it.
  3. Segments — who, in priority order, and who is explicitly out of scope this period.
  4. Channel mix — three tiers:
    • Proven — working now; fund to capacity, then stop. Most channels have a ceiling and spending past it buys worse customers.
    • Scaling — evidence but not yet at capacity; the growth budget.
    • Experimental — capped at a share you can lose entirely without missing the objective.
  5. Sequencing — what has to be true before each thing starts. Content before paid, positioning before content.
  6. Budget — by tier and channel, with the fixed-versus-variable split visible.
  7. Measurement — the leading indicator per channel and when it should first move. A channel with no stated read-by date runs forever.
  8. Kill criteria — what result stops each experiment. Decided in advance, when it is cheap.

Pressure-test before committing

  • What must be true for this to work, and which of those is least certain?
  • What happens at half the budget? If the plan collapses, it has no core.
  • Which line item would you cut first? If nothing, the plan is not prioritized.
  • Where does this depend on another team delivering, and have they agreed?

Sources

references/sources.md in this skill lists the outside authorities that settle the questions here — what each one is authoritative for, and what you may do with it. Check them before answering on anything they cover, and cite what you used. Most are free to read and not free to reproduce; the use note on each is binding.

Never

  • Plan channel activity before positioning is settled.
  • Fund an experiment you cannot afford to have fail.
  • Report a plan without stating what did not get funded and why.

レビュー

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

同じリポジトリのスキル

概要と使いどころ

Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process. Use this to design a permissions model, run an access review, reduce standing privilege, handle offboarding, set up SSO or MFA, manage service and machine credentials, or diagnose why permissions have sprawled.

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

cbrock84/headcount2,0372026年9月18日 更新

Concentrates marketing and sales effort on a named set of accounts rather than on volume — qualifying whether the model fits your economics at all, building the account list and the buying group inside each, tiering effort against account value, coordinating so the account experiences one campaign rather than several, and measuring account progression instead of leads. Use this to decide whether to run an account-based program, build one, or work out why an existing one produces activity and no pipeline.

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

cbrock84/headcount2,0372026年9月18日 更新

Gets new users from signup to first real value — signup flow, onboarding, time-to-value, and the early experience that determines whether someone becomes a user or a lapsed account. Use this to design or fix signup and onboarding, diagnose why signups do not convert to active use, reduce time-to-value, or decide what a new user must accomplish first.

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

cbrock84/headcount2,0372026年9月18日 更新

Designs orchestrator-and-subagent hierarchies for a repository — splitting agents by exclusive write surface, pairing every producer with an independent auditor, and enforcing the split with a script that runs in CI. Use this whenever the user wants to set up, expand, audit, or fix a multi-agent or subagent structure for a codebase; asks how to divide work between agents; wants agent charters, roles, or a surface map written; or is hitting agents that collide on the same files, review their own work, or drift from their remit. Also use when sizing a roster or deciding whether a new agent is justified.

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

cbrock84/headcount2,0372026年9月18日 更新

Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire. Use this before deploying a model or AI feature, when defining evaluation criteria, when a model's behavior has drifted, when assessing AI risk or regulatory exposure, or when deciding whether an AI system is fit for a consequential decision.

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

cbrock84/headcount2,0372026年9月18日 更新

Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with the confidence in each claim made explicit. Use this to analyze a market or industry, map competitors, evaluate a market-entry or build-versus-buy decision, produce a research brief, or assemble evidence for a decision. Also use when comparing options that need a structured, evidence-based verdict rather than an opinion.

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

cbrock84/headcount2,0372026年9月18日 更新

cbrock84 のスキルをすべて見る

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