campaign-file

/campaign-file

Entry point for the strategist agent. You have a signal — you want a brief the copywriter can act on. This skill loads context, delegates to strategist, and reports the result.

Always do first

Read .claude/project.yaml and confirm there's a populated marketing: block:

• marketing.audiences.path exists and has at least one ICP file
• marketing.brand.voice_file exists at the named path
• marketing.channels.enabled has at least one channel
• marketing.goals.primary_metric is non-empty

If any of these is missing, surface and direct the user to /bootstrap-marketing (or /voice-define if only the voice file is missing) before proceeding. A brief written against a misconfigured manifest is worse than no brief.

Take the signal

The signal comes from one of three places, in priority order:

1. The user's invocation argument. If /campaign-file <signal> was run, that's the signal — confirm before proceeding ("you want a brief about: ''. Right?").
2. Open conversation. If the user just described a signal in chat, use that. Confirm before delegating.
3. Ask. If neither, ask: "What's the signal? — a recent release, a customer win, a competitive move, a platform launch, a seasonality moment, or something else."

Don't accept "we should post something this week" as a signal. That's not a signal, that's a calendar slot. Push back and ask what's actually happening.

Delegate to strategist

Spawn the strategist agent with the confirmed signal as the entry context. Strategist will:

1. Load the full marketing context (manifest, voice, ICPs, playbook, profile, recent campaigns)
2. Pick the ICP the signal maps to (if ambiguous, surface options)
3. Write marketing/campaigns/<YYYY-MM-DD>-<slug>/brief.md
4. Return the path, the ICP, the success metric, and any open Decisions

Report back

Show the user:

• Link to the brief
• ICP chosen + one-line reason
• Success metric + window
• Distribution mix summary
• Any open Decisions (so the user knows what they owe before /content-draft can run)

Suggested next step:

• If open Decisions exist: "Resolve the open Decisions in the brief, then re-run /campaign-file to refresh or proceed manually."
• If no open Decisions: "Brief is hand-off-ready. Next: /content-draft <brief-path> to have copywriter produce the drafts."

What this skill doesn't do

• Draft content (that's the eventual /content-draft skill, which spawns copywriter)
• Publish anything
• Modify VOICE.md, ICPs, or PLAYBOOK.md
• File a brief against a repo without marketing: configured