AgentKit
DocsKitsCLI ReferenceDesktop App
BetaYou are reading docs for the beta channel (2.13.0-beta.20). Features may change before the next stable release.Switch to stable →

Skills

Turn approved evidence into a marketing plan with ak:marketing-planning

Create a self-contained marketing decision artifact with strategy, phases, owners, measures, risks, and approvals while stopping before campaign execution.

Use ak:marketing-planning to transform a marketing goal and reviewed evidence into an organized plan. The Skill can design positioning, channels, campaign phases, deliverables, measures, and contingencies; it must not execute the campaign.

Choose planning for a decision artifact

Use ak:marketing-planning when

  • You need a campaign, launch, content strategy, editorial calendar, funnel, or multi-channel initiative broken into reviewable phases.
  • You need to compare strategy options through RACE, SOSTAC, STP, SMART goals, or another relevant decision frame.
  • You need owners, dependencies, deliverables, approval requirements, measures, risks, and unresolved questions documented together.

Choose another workflow when

  • Market, competitor, or audience evidence is missing. Start with ak:marketing-research; the planning Skill also invokes that research phase unless reviewed reports are supplied.
  • You need ideas before choosing a strategy. Use ak:marketing-ideas.
  • You need campaign execution, publication, ads, outreach, asset production, or account changes. Approve and run the relevant execution workflow separately.

Prepare evidence, constraints, and decisions

Supply the business goal, target audience, market and competitor research, brand authority, prior campaign evidence, current assets, resources, timeline, channels under consideration, measurement capability, compliance constraints, and decision owners. If reviewed research or brand documents already exist, identify them so the corresponding discovery phase can be skipped.

State budget, KPI, target, and deadline values as approved inputs or explicitly ask for proposals. The Skill's plan format can populate these fields, but an inferred value is not a financial commitment, forecast, or performance fact.

Invoke a bounded planning goal

RuntimeInvocationAvailability boundary
Claude Code/ak:marketing-planning ...Can use native plan context and bundled helper paths when installed and active.
Cursor/ak:marketing-planning ...Slash invocation is user-verified; plan Hooks and helpers can differ.
Codex$ak:marketing-planning ...Uses native Skill discovery; plan-state injection and supporting automation are runtime-specific.
/ak:marketing-planning "Create a 6-week launch plan from the approved audience and competitor reports. Propose two channel mixes, label unapproved budget and KPI values as drafts, include owners and approval gates, and do not publish, spend, or contact anyone"

Understand the six stages

  1. Analyze current context. Discover the project's brand, marketing, business, product, campaign, asset, sales, measurement, and compliance authorities instead of assuming filenames beyond documented defaults.
  2. Research missing evidence. Run the research phase for market, competitors, audience, trends, and benchmarks, or skip it when reviewed reports are supplied.
  3. Synthesize opportunities. Identify supported positioning options, audience needs, trade-offs, conflicts, and assumptions.
  4. Design strategy. Define positioning, messages, journey, channel options, campaign architecture, resources, proposed budget, measures, tests, risks, and contingencies.
  5. Document the plan. Create plan.md, research and report artifacts, and phase-XX-phase-name.md files in the selected plan directory.
  6. Review and refine. Check feasibility, brand alignment, evidence, dependencies, approval gates, measurability, and unresolved questions, then return the plan path and summary without execution.

When runtime plan context shows an active plan, the workflow asks before continuing it. A suggested plan is only a hint and must not be auto-used. On new plan creation, the source calls .claude/scripts/set-active-plan.cjs; do not assume that Claude-specific helper or Hook context exists unchanged elsewhere.

Keep planning separate from authority

A plan proposes external actions; it does not approve them

Channel allocation, budget, targeting, pricing, offers, claims, deadlines, providers, tests, and expected results remain proposals until the responsible owner approves them against current evidence and policy.

The workflow writes local planning artifacts and may update active-plan session state where supported. It must not buy media, create provider accounts, change CRM or analytics state, upload audiences, contact people, contract a vendor, publish assets, deploy code, or spend money. Each such action needs separate scope, credentials, review, and approval.

Verify the plan and evidence

A decision-ready plan should include:

  • Source-linked research, brand authority, assumptions, and evidence gaps.
  • Objective, audience, positioning options, rationale, and rejected alternatives.
  • Phases, deliverables, owners, dependencies, dates, and approval requirements.
  • Proposed channels, resources, budget, KPIs, benchmarks, attribution limits, tests, risks, contingencies, and stop conditions.
  • Required YAML frontmatter in plan.md, with new plans starting at status: pending and every unapproved numeric value visibly marked as draft.
  • Exact artifact paths, review status, and unresolved stakeholder decisions.

Troubleshoot and know the limits

SymptomSafe next step
Research or brand authority is absentPause for approved inputs or run the bounded research phase; do not invent customer or brand facts.
Plan context shows “Suggested”Ask whether to activate it or create a new plan; do not write reports into the suggestion automatically.
Budget or KPI values are unknownUse ranges or placeholders labeled as proposals and assign an owner to approve them.
A framework conflicts with the evidenceAdapt or omit the framework; RACE, SOSTAC, STP, and SMART are aids, not mandatory proof.
The user asks to launch from this SkillFinish the plan and stop; request separate authorization for the exact execution workflow.

The Skill does not validate provider availability, quote live media prices, forecast revenue, guarantee attribution, or prove a plan is feasible. Its sample frontmatter values and allocations are illustrative, not defaults. Continue with Projects, artifacts, and checkpoints and the Marketing Kit lifecycle for ownership and recovery.