campaign-brief
Produces a campaign brief that an empowered team can execute without needing a follow-up meeting. Every brief is anchored to one phase of the customer journey (Before/During/After) using Allan Dib's 1-Page Marketing Plan. Phase determines channels, assets, and success metrics - not the other way around.
When to use
- "Plan a campaign for our Q3 launch"
- "Build a GTM plan for "
- "Brief a demand gen campaign targeting CMOs"
- "Write the launch plan for the integration with X"
- "We need a marketing plan for <event/feature/audience>"
Framework: Before/During/After (Allan Dib, The 1-Page Marketing Plan)
Every campaign primarily serves one phase. Force the choice before building anything else.
BEFORE - Prospects who don't know you exist.
- Goal: get strangers to raise their hand
- Focus: reach, awareness, USP clarity
- Channels: paid social, SEO, PR, cold outreach, events, partner content
- Success metrics: reach, impressions, hand-raisers (leads generated), CPL
DURING - Leads who know you but haven't bought.
- Goal: convert interest into purchase
- Focus: lead capture, nurture, trust-building, sales conversion
- Channels: email sequences, retargeting, demos, webinars, case studies
- Success metrics: MQLs, SQLs, demo bookings, trial starts, conversion rate
AFTER - Customers who have already bought.
- Goal: create raving fans who expand and refer
- Focus: world-class experience, upsell, cross-sell, referrals
- Channels: customer comms, CSM touchpoints, loyalty programs, referral incentives
- Success metrics: NPS, expansion revenue, referrals generated, churn rate, LTV
A campaign cannot serve all 3 phases at once. If the user wants all 3, split it into 3 campaigns.
Inputs needed
Walk the user through these one at a time. Do not skip.
- Campaign phase: Before, During, or After? If the user isn't sure, ask: "Are you trying to reach new people, convert known leads, or grow existing customers?" Force a single answer.
- Campaign goal: one sentence, tied to the phase.
- Primary KPI: the one number that defines success. With a target.
- Audience: which persona from
knowledge/icp/personas.md. If multiple, force-rank.
- Window: start date, end date (DD-MM-YYYY).
- Budget: total, or "no paid budget".
- Constraints: legal, brand, channel restrictions, dependencies on other teams.
- What's already decided: any creative, channel, or partner choices the user has locked in.
Process
Load context. Read all reads: files. If knowledge/icp/personas.md is missing, stop and run /brand-context.
Identify the phase. Before generating any brief content, confirm the Before/During/After phase with the user. State it explicitly: "This is a BEFORE campaign. The goal is to generate hand-raisers from people who don't yet know us."
Check knowledge/learnings.md for any relevant past campaign retros. Reference them in the brief.
Generate the brief in this format:
# <Campaign name>
**Phase**: BEFORE | DURING | AFTER (Allan Dib framework)
**Phase goal**: <get hand-raisers | convert leads | grow customers>
**Campaign goal**: <one sentence, single-objective>
**Primary KPI**: <metric> -> target <number> by <DD-MM-YYYY>
**Window**: DD-MM-YYYY to DD-MM-YYYY
**Budget**: $<amount> or <none>
**Owner**: <person, ask the user>
**Status**: draft
## Audience
- **Primary persona**: <from knowledge/icp/>
- **Top 3 pains we are speaking to**:
1. ...
2. ...
3. ...
- **Where they are**: channels, communities, publications
## Message
- **Core message** (one sentence the audience should remember):
- **Proof points** (3 max). Each must be lifted from `knowledge/company.md` verified proof points
with the source named inline. If fewer than three verified proof points exist, ship fewer: write
[NO VERIFIED PROOF POINT] and move it to Open questions. Never generate a proof point -
these flow straight into /linkedin-post and /landing-page-writer and become public claims:
1. ...
2. ...
3. ...
- What we are NOT saying: explicit anti-messages to avoid scope creep
Strategy
- Why now (timing rationale):
- Differentiation vs (how this plays where we win):
- What we learned from (from knowledge/learnings.md):
Channel mix
Channels must match the campaign phase. BEFORE = reach channels. DURING = conversion channels. AFTER = retention channels.
| Channel |
Role |
Asset count |
Spend |
Owner |
| LinkedIn organic |
Awareness |
8 posts |
$0 |
|
| LinkedIn ads |
Demand |
3 ad sets |
$X |
|
| Email nurture |
Conversion |
5-email sequence |
$0 |
|
| ... |
|
|
|
|
Assets needed
Group by team. Be specific.
- Content: 1 pillar article (1800w), 8 LinkedIn posts, 3 quote graphics
- Design: 1 landing page hero image, 3 ad creatives, 1 email header
- Video: 1 explainer (60s)
- Sales enablement: 1 one-pager, 1 deck update
- Web: 1 landing page
Timeline
Working backward from launch date.
| Week |
Milestone |
Owner |
| -4 |
Brief approved, assets briefed |
|
| -3 |
First drafts in review |
|
| -2 |
Final assets, landing page live |
|
| -1 |
Soft launch, internal alignment |
|
| 0 |
Launch |
|
| +1 |
First metrics review |
|
| +4 |
Campaign retro |
|
Success metrics
Phase-specific. Do not mix metrics from other phases.
BEFORE campaigns:
- Primary: <reach | CPL | hand-raisers generated> =
- Secondary: impressions, CTR, email sign-ups
- Leading indicators (visible by week 1): ad CTR, organic post reach
- Lagging indicators (visible by week 4): total leads captured, CPL
DURING campaigns:
- Primary: <MQLs | SQLs | demo bookings | trials> =
- Secondary: email open rate, demo-to-close rate
- Leading indicators (visible by week 1): email opens, landing page CVR
- Lagging indicators (visible by week 4): total SQLs, pipeline generated
AFTER campaigns:
- Primary: <NPS | referrals | expansion revenue | churn rate> =
- Secondary: product usage, upsell conversion, CSAT
- Leading indicators (visible by week 1): feature adoption, support tickets
- Lagging indicators (visible by week 4): NPS score, referrals, expansion ARR
Risks and mitigations
Open questions
- List anything you do not have an answer to. Do not invent.
Approvals
5. **Self-check**:
- Phase is declared and all elements serve that phase
- Channels match the phase (no conversion channels in a BEFORE campaign, no awareness channels in an AFTER campaign)
- Single primary KPI - not three
- Specific persona, not "marketers"
- Working-backward timeline, not aspirational
- Concrete assets list with counts
- References at least one prior learning if `knowledge/learnings.md` exists
- Phase-specific success metrics only
6. **Save** to `output/campaign-brief/<DD-MM-YYYY>-<slug>.md` with frontmatter:
```yaml
---
format: campaign-brief
campaign: <name>
phase: <before|during|after>
goal: <awareness|demand|expansion|retention|recruitment>
start: DD-MM-YYYY
end: DD-MM-YYYY
primary-kpi: <metric>
target: <number>
budget: <amount or none>
created: DD-MM-YYYY
---
- Offer next actions:
- Generate the asset list as individual skill calls (
/linkedin-post x 8, /landing-page-writer x 1, etc.)
- Build the launch deck (
/ppt-maker)
- Remind the user: "Set a calendar reminder to run
/retro on [launch date + 28 days] to capture learnings."
Rules
- Declare the phase before writing a single line of the brief. Phase determines everything else.
- One primary KPI. If the user names three, force them to rank and pick one.
- Channel mix must match the phase. A BEFORE campaign with a demo CTA is a contradiction. Call it out.
- Never copy a previous campaign brief without reading
knowledge/learnings.md first. Past failures should change current plans.
- If budget is zero, do not propose paid channels. Reallocate to organic.
- Timeline must be working backward from launch. If the user gives a launch date, derive milestones from it. If not, ask.
- If the user wants to run a BEFORE and DURING campaign simultaneously, produce two separate briefs. Mixed-phase campaigns are unfocused campaigns.
Handling [UNVERIFIED] and [NEEDS INPUT] tags
brand-context tags any number the user was unsure of as [UNVERIFIED], and several skills tag
gaps as [NEEDS INPUT]. Those tags are a contract, and it only works if this skill honours it.
- Carry the tag forward. If a baseline, benchmark or proof point arrives tagged, every figure
derived from it is tagged too. A target built on an unverified baseline is an unverified target.
- Never silently promote. Do not drop the tag because the number looked confident in the
source file.
- Say it in the output. List every tagged input in its own line near the top, so a reader
knows which numbers are measured and which are estimates before they act on them.
- A decision that would change if the tagged number were wrong must say so explicitly.
The Before / During / After model (Allan Dib)
Allan Dib's The 1-Page Marketing Plan splits a campaign into three phases with different jobs,
different audiences and different metrics. Most failed campaigns are a During-phase tactic aimed at
a Before-phase audience.
| Phase |
Audience |
Job |
Primary metric |
Typical channels |
| Before |
They do not know you |
Earn attention and permission |
Reach, new subscribers |
Content, paid awareness, PR, partnerships |
| During |
They know you, have not bought |
Convert interest into a decision |
Conversion rate, pipeline |
Email, retargeting, demos, sales enablement |
| After |
They bought |
Retain, expand, get referrals |
Retention, expansion, referral rate |
Onboarding, community, case studies |
One campaign, one phase. A brief covering all three is a strategy document, not a campaign, and
it produces channel plans nobody can execute. Pick the phase, then choose channels that serve it.
Decision thresholds
| Signal |
Threshold |
What to do |
| Phases in scope |
More than 1 |
Split into separate briefs, sequenced |
| Primary KPIs |
More than 1 |
Pick one. The rest are supporting metrics |
| Verified proof points |
Fewer than 3 |
Ship fewer and move the gap to Open questions. Never generate one |
| Baseline for the target |
Missing or [UNVERIFIED] |
Tag the target, and state which decisions change if the baseline is wrong |
| Channels planned |
More than 4 for one phase |
Cut. Thin coverage across many channels beats nothing, but not by much |
Related skills
/brand-context owns knowledge/company.md, the source of verified proof points
/social-calendar turns the content line of this brief into a dated schedule
/kpi-review reads the results against the target set here
/retro runs after the campaign and writes reusable learnings back
/growth-experiment when a channel in the plan is unproven for this audience
What this skill cannot know
- Whether the team has capacity to produce the assets this brief plans. Ask before finalising
- Whether the budget figure is approved or aspirational
- Whether a channel worked for this audience before, unless it is in
knowledge/learnings.md
- Whether the target derived from an
[UNVERIFIED] baseline is reachable
1---2name: campaign-brief3description: Plan a marketing campaign end-to-end using Allan Dib's Before/During/After framework (The 1-Page Marketing Plan). Produces a phase-specific campaign brief with goal, audience, message, channels, assets, timeline, budget, and success metrics. Use when the user asks to plan a campaign, brief a campaign, "we need a campaign for X", launch plan, GTM plan, marketing plan for [product], demand gen plan, or any multi-channel marketing initiative. Reads ICP, services, and KPIs from knowledge/. For a full quarterly strategy rather than one campaign, see marketing-plan scope in positioning-doc and kpi-review. For the content schedule inside the campaign, see social-calendar. For the post-campaign review, see retro.4metadata:5 source: https://skillmd.com/skills/qa-aman/campaign-brief6 grounded_in:7 - "1-Page Marketing Plan (Before/During/After) - Allan Dib"8 reads:9 - knowledge/icp/personas.md10 - knowledge/services/11 - knowledge/markets/positioning.md12 - knowledge/markets/competitors.md13 - knowledge/kpis.md14 - knowledge/learnings.md15 - knowledge/company.md16 writes:17 - output/campaign-brief/18---1920# campaign-brief2122Produces a campaign brief that an empowered team can execute without needing a follow-up meeting. Every brief is anchored to one phase of the customer journey (Before/During/After) using Allan Dib's 1-Page Marketing Plan. Phase determines channels, assets, and success metrics - not the other way around.2324## When to use2526- "Plan a campaign for our Q3 launch"27- "Build a GTM plan for <product>"28- "Brief a demand gen campaign targeting CMOs"29- "Write the launch plan for the integration with X"30- "We need a marketing plan for <event/feature/audience>"3132## Framework: Before/During/After (Allan Dib, The 1-Page Marketing Plan)3334Every campaign primarily serves one phase. Force the choice before building anything else.3536**BEFORE** - Prospects who don't know you exist.37- Goal: get strangers to raise their hand38- Focus: reach, awareness, USP clarity39- Channels: paid social, SEO, PR, cold outreach, events, partner content40- Success metrics: reach, impressions, hand-raisers (leads generated), CPL4142**DURING** - Leads who know you but haven't bought.43- Goal: convert interest into purchase44- Focus: lead capture, nurture, trust-building, sales conversion45- Channels: email sequences, retargeting, demos, webinars, case studies46- Success metrics: MQLs, SQLs, demo bookings, trial starts, conversion rate4748**AFTER** - Customers who have already bought.49- Goal: create raving fans who expand and refer50- Focus: world-class experience, upsell, cross-sell, referrals51- Channels: customer comms, CSM touchpoints, loyalty programs, referral incentives52- Success metrics: NPS, expansion revenue, referrals generated, churn rate, LTV5354A campaign cannot serve all 3 phases at once. If the user wants all 3, split it into 3 campaigns.5556## Inputs needed5758Walk the user through these one at a time. Do not skip.59601. **Campaign phase**: Before, During, or After? If the user isn't sure, ask: "Are you trying to reach new people, convert known leads, or grow existing customers?" Force a single answer.612. **Campaign goal**: one sentence, tied to the phase.623. **Primary KPI**: the one number that defines success. With a target.634. **Audience**: which persona from `knowledge/icp/personas.md`. If multiple, force-rank.645. **Window**: start date, end date (DD-MM-YYYY).656. **Budget**: total, or "no paid budget".667. **Constraints**: legal, brand, channel restrictions, dependencies on other teams.678. **What's already decided**: any creative, channel, or partner choices the user has locked in.6869## Process70711. **Load context.** Read all `reads:` files. If `knowledge/icp/personas.md` is missing, stop and run `/brand-context`.72732. **Identify the phase.** Before generating any brief content, confirm the Before/During/After phase with the user. State it explicitly: "This is a BEFORE campaign. The goal is to generate hand-raisers from people who don't yet know us."74753. **Check `knowledge/learnings.md`** for any relevant past campaign retros. Reference them in the brief.76774. **Generate the brief in this format**:7879 ```80 # <Campaign name>8182 **Phase**: BEFORE | DURING | AFTER (Allan Dib framework)83 **Phase goal**: <get hand-raisers | convert leads | grow customers>84 **Campaign goal**: <one sentence, single-objective>85 **Primary KPI**: <metric> -> target <number> by <DD-MM-YYYY>86 **Window**: DD-MM-YYYY to DD-MM-YYYY87 **Budget**: $<amount> or <none>88 **Owner**: <person, ask the user>89 **Status**: draft9091 ## Audience92 - **Primary persona**: <from knowledge/icp/>93 - **Top 3 pains we are speaking to**:94 1. ...95 2. ...96 3. ...97 - **Where they are**: channels, communities, publications9899 ## Message100 - **Core message** (one sentence the audience should remember):101 - **Proof points** (3 max). Each must be lifted from `knowledge/company.md` verified proof points102 with the source named inline. If fewer than three verified proof points exist, ship fewer: write103 `[NO VERIFIED PROOF POINT]` and move it to Open questions. **Never generate a proof point** -104 these flow straight into `/linkedin-post` and `/landing-page-writer` and become public claims:105 1. ...106 2. ...107 3. ...108 - **What we are NOT saying**: explicit anti-messages to avoid scope creep109110 ## Strategy111 - **Why now** (timing rationale):112 - **Differentiation vs <competitor>** (how this plays where we win):113 - **What we learned from <past campaign>** (from knowledge/learnings.md):114115 ## Channel mix116 Channels must match the campaign phase. BEFORE = reach channels. DURING = conversion channels. AFTER = retention channels.117118 | Channel | Role | Asset count | Spend | Owner |119 |---|---|---|---|---|120 | LinkedIn organic | Awareness | 8 posts | $0 | <name> |121 | LinkedIn ads | Demand | 3 ad sets | $X | <name> |122 | Email nurture | Conversion | 5-email sequence | $0 | <name> |123 | ... | | | | |124125 ## Assets needed126 Group by team. Be specific.127 - **Content**: 1 pillar article (1800w), 8 LinkedIn posts, 3 quote graphics128 - **Design**: 1 landing page hero image, 3 ad creatives, 1 email header129 - **Video**: 1 explainer (60s)130 - **Sales enablement**: 1 one-pager, 1 deck update131 - **Web**: 1 landing page132133 ## Timeline134 Working backward from launch date.135 | Week | Milestone | Owner |136 |---|---|---|137 | -4 | Brief approved, assets briefed | |138 | -3 | First drafts in review | |139 | -2 | Final assets, landing page live | |140 | -1 | Soft launch, internal alignment | |141 | 0 | Launch | |142 | +1 | First metrics review | |143 | +4 | Campaign retro | |144145 ## Success metrics146 Phase-specific. Do not mix metrics from other phases.147148 **BEFORE campaigns**:149 - **Primary**: <reach | CPL | hand-raisers generated> = <target>150 - **Secondary**: impressions, CTR, email sign-ups151 - **Leading indicators** (visible by week 1): ad CTR, organic post reach152 - **Lagging indicators** (visible by week 4): total leads captured, CPL153154 **DURING campaigns**:155 - **Primary**: <MQLs | SQLs | demo bookings | trials> = <target>156 - **Secondary**: email open rate, demo-to-close rate157 - **Leading indicators** (visible by week 1): email opens, landing page CVR158 - **Lagging indicators** (visible by week 4): total SQLs, pipeline generated159160 **AFTER campaigns**:161 - **Primary**: <NPS | referrals | expansion revenue | churn rate> = <target>162 - **Secondary**: product usage, upsell conversion, CSAT163 - **Leading indicators** (visible by week 1): feature adoption, support tickets164 - **Lagging indicators** (visible by week 4): NPS score, referrals, expansion ARR165166 ## Risks and mitigations167 - **Risk**: <what could go wrong>168 **Mitigation**: <what we do about it>169170 ## Open questions171 - List anything you do not have an answer to. Do not invent.172173 ## Approvals174 - [ ] Marketing lead175 - [ ] Product176 - [ ] Sales177 - [ ] Legal (if applicable)178 ```1791805. **Self-check**:181 - Phase is declared and all elements serve that phase182 - Channels match the phase (no conversion channels in a BEFORE campaign, no awareness channels in an AFTER campaign)183 - Single primary KPI - not three184 - Specific persona, not "marketers"185 - Working-backward timeline, not aspirational186 - Concrete assets list with counts187 - References at least one prior learning if `knowledge/learnings.md` exists188 - Phase-specific success metrics only1891906. **Save** to `output/campaign-brief/<DD-MM-YYYY>-<slug>.md` with frontmatter:191 ```yaml192 ---193 format: campaign-brief194 campaign: <name>195 phase: <before|during|after>196 goal: <awareness|demand|expansion|retention|recruitment>197 start: DD-MM-YYYY198 end: DD-MM-YYYY199 primary-kpi: <metric>200 target: <number>201 budget: <amount or none>202 created: DD-MM-YYYY203 ---204 ```2052067. **Offer next actions**:207 - Generate the asset list as individual skill calls (`/linkedin-post` x 8, `/landing-page-writer` x 1, etc.)208 - Build the launch deck (`/ppt-maker`)209 - Remind the user: "Set a calendar reminder to run `/retro` on [launch date + 28 days] to capture learnings."210211## Rules212213- Declare the phase before writing a single line of the brief. Phase determines everything else.214- One primary KPI. If the user names three, force them to rank and pick one.215- Channel mix must match the phase. A BEFORE campaign with a demo CTA is a contradiction. Call it out.216- Never copy a previous campaign brief without reading `knowledge/learnings.md` first. Past failures should change current plans.217- If budget is zero, do not propose paid channels. Reallocate to organic.218- Timeline must be working backward from launch. If the user gives a launch date, derive milestones from it. If not, ask.219- If the user wants to run a BEFORE and DURING campaign simultaneously, produce two separate briefs. Mixed-phase campaigns are unfocused campaigns.220221## Handling [UNVERIFIED] and [NEEDS INPUT] tags222223`brand-context` tags any number the user was unsure of as `[UNVERIFIED]`, and several skills tag224gaps as `[NEEDS INPUT]`. Those tags are a contract, and it only works if this skill honours it.2252261. **Carry the tag forward.** If a baseline, benchmark or proof point arrives tagged, every figure227 derived from it is tagged too. A target built on an unverified baseline is an unverified target.2282. **Never silently promote.** Do not drop the tag because the number looked confident in the229 source file.2303. **Say it in the output.** List every tagged input in its own line near the top, so a reader231 knows which numbers are measured and which are estimates before they act on them.2324. **A decision that would change if the tagged number were wrong must say so explicitly.**233234## The Before / During / After model (Allan Dib)235236Allan Dib's *The 1-Page Marketing Plan* splits a campaign into three phases with different jobs,237different audiences and different metrics. Most failed campaigns are a During-phase tactic aimed at238a Before-phase audience.239240| Phase | Audience | Job | Primary metric | Typical channels |241|---|---|---|---|---|242| **Before** | They do not know you | Earn attention and permission | Reach, new subscribers | Content, paid awareness, PR, partnerships |243| **During** | They know you, have not bought | Convert interest into a decision | Conversion rate, pipeline | Email, retargeting, demos, sales enablement |244| **After** | They bought | Retain, expand, get referrals | Retention, expansion, referral rate | Onboarding, community, case studies |245246**One campaign, one phase.** A brief covering all three is a strategy document, not a campaign, and247it produces channel plans nobody can execute. Pick the phase, then choose channels that serve it.248249## Decision thresholds250251| Signal | Threshold | What to do |252|---|---|---|253| Phases in scope | More than 1 | Split into separate briefs, sequenced |254| Primary KPIs | More than 1 | Pick one. The rest are supporting metrics |255| Verified proof points | Fewer than 3 | Ship fewer and move the gap to Open questions. Never generate one |256| Baseline for the target | Missing or `[UNVERIFIED]` | Tag the target, and state which decisions change if the baseline is wrong |257| Channels planned | More than 4 for one phase | Cut. Thin coverage across many channels beats nothing, but not by much |258259## Related skills260261- `/brand-context` owns `knowledge/company.md`, the source of verified proof points262- `/social-calendar` turns the content line of this brief into a dated schedule263- `/kpi-review` reads the results against the target set here264- `/retro` runs after the campaign and writes reusable learnings back265- `/growth-experiment` when a channel in the plan is unproven for this audience266267## What this skill cannot know268269- Whether the team has capacity to produce the assets this brief plans. Ask before finalising270- Whether the budget figure is approved or aspirational271- Whether a channel worked for this audience before, unless it is in `knowledge/learnings.md`272- Whether the target derived from an `[UNVERIFIED]` baseline is reachable