Grassroots-first campaign design for anyone being outspent — startups vs. incumbents, NGOs vs. corporate comms, movements vs. state-backed machines, solo brands vs. big-budget competitors. Ideates awareness, launch, fundraising, mobilization, community-build, counter-narrative, referral, founder-story, and coalition campaigns. Triggers on "campaign plan", "marketing strategy", "ad budget", "should I advertise", "paid vs organic", "launch plan", "grassroots", "low budget marketing", "NGO campaign", "outspent", "competitor has bigger budget", "how do I compete without money". Also trigger on any spend asymmetry, collapsing organic reach, rising CPAs, or a trust/credibility problem — even without the word "campaign". Nudge activation when the user debates buying ads, boosting posts, or hiring influencers; they are likely about to burn money on a channel that will not persuade.
87
85%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
A campaign-design skill for organizations and people who cannot win by outspending. It ideates campaign concepts across every major archetype, audits the user's spend asymmetry against their competition, assembles an organic-first channel stack, sets strict boost gates on any paid spend, and produces a lift-test plan so the user measures incremental impact rather than vanity metrics.
Paid media scales attention. Organic narrative and grassroots networks scale trust. When trust is the bottleneck — and in 2025–2026, for most underdogs, it is — additional ad spend hits diminishing and then negative returns. Saturation, inauthenticity, and narrative incoherence produce reactance, not persuasion. The leverage point is not reach; it is credibility and message-market fit.
Empirical spine:
references/hungarian-case-study.md.The same curve bends commercial advertising. The skill treats paid as an amplifier of proven organic winners, never as a standalone channel.
Apply when the user:
Also apply when no explicit "campaign" is named but the user is debating where to invest time and money for distribution.
The skill runs in six stages (1, 2, 3, 3a, 4, 5). Do not skip stages; later stages depend on the user's answers and selections from earlier ones. Stage 3a (MMF Gate) can refuse the full campaign plan and route the user to validation work instead.
The skill has three intake modes. Pick the mode that matches the user's brief before asking any questions.
Mode A — Full-brief mode. The user has volunteered all 8 fields below up front (in a pasted brief, a prior plan, a detailed message). Skip the interview entirely, confirm understanding in one sentence, and proceed to Stage 2.
Mode B — Interview mode. The user explicitly asks to be scoped ("help me figure
out what this campaign should be," "walk me through it," "interview me"). Ask the 8
questions below via AskUserQuestion in batches of ≤4 per call. Do not invent
answers. Do not merge questions.
Mode C — Default mode (for terse briefs). The user gave a short brief (≤2 sentences) without asking for an interview. This is the common case. Do NOT run the full 8-question interview — it turns a 12-word prompt into an interrogation. Instead:
Always-capture fields (ask once, batched). Four fields are too material to
default silently; getting them wrong produces a generic plan. Send one
AskUserQuestion call with up to 4 questions covering:
references/sector-riders.md
(cohort-education, b2b-saas, ngo, consumer-brand, political-civic,
personal-brand), or other with a one-sentence description. The sector
rider materially changes Stage 4 channel weighting and Stage 5 archetype
defaults.If one of these four fields is already clearly present in the user's brief,
drop it from the AskUserQuestion call. Only ask what is missing.
Default-with-flag fields. The remaining fields default silently but are surfaced in an Assumptions table at the top of the final deliverable (Stage 5 output). The user can confirm or adjust inline after reading the plan:
| Field | Default under terse brief |
|---|---|
| Competition (specifics) | Abstract — "cohort-based courses in the category," "mid-size SaaS competitors," etc. Use the heuristic questions in references/asymmetry-audit-table.md to classify asymmetry qualitatively. Never invent specific competitor names. |
| Existing channels / traction | "Starting from zero" unless the user's brief, working directory, or CLAUDE.md clearly indicates an existing newsletter, community, or follower base. |
| Bottleneck | Trust (the 2025–2026 default for almost every underdog campaign). |
| Time window | 60 days to a single dated anchor moment (event, launch, election), then recurring cadence. |
| Capacity | 6h/week. |
Escalation rule. If a missing field would materially change the Stage 3
asymmetry classification or the Stage 4 primary-function choice, do not
default it — add it to the AskUserQuestion call. Example: if the user
mentions "our whole team is posting already" but does not specify which
channels, ask, because it changes the channel stack.
Assumptions table is mandatory under Mode C. Open the final deliverable with a table listing every defaulted field and its assumed value. End the deliverable with: "Confirm or adjust any row in the Assumptions table and I will re-run the affected stages."
Regardless of mode, the campaign plan is grounded in these 8 fields:
references/asymmetry-audit-table.md heuristics. Never invent names.
(Defaults in Mode C; user can sharpen in the Assumptions confirmation.)Before any audit or channel work, generate at least five distinct campaign concepts,
drawn from different archetypes in references/campaign-archetypes.md. Do not converge
early. The point is to give the user a shaped menu to choose from.
For each concept, produce:
references/channel-tier-stack.md this
concept leans on (Tier 1/2/3/4).Anti-fabrication rule for concept names, theses, and hooks. If the user named a
specific competitor in the brief, use the name. If the user said "well-known incumbent,"
"market leader," "the dominant player," or otherwise did not name one, do not fill in
the blank with your best guess. Stay at the level of abstraction the brief gave you.
Use the category descriptor (e.g., "the $400-per-seat monitor"), the behavior
("the enterprise billing tax"), or a bracketed placeholder ([incumbent]) that the user
will fill in. Concept names like "We Quit Sentry" or "DataDog Alternative" — invented
from the category description rather than the brief — violate the Stage 1 anti-fabrication
rule and must not appear in Stage 2 output. This applies equally to SEO keyword lists,
earned-media pitch hooks, and any downstream section that inherits the concept name.
Industry-peer rule. The anti-fabrication rule covers any competitor name absent from the brief — not only invented names, but widely-known industry peers to a brief-named incumbent. If the brief names one dominant player (e.g., the user says "we're outspent 100x by [market leader]"), do not add the obvious #2 or #3 from the same category on your own ("LexisNexis and Westlaw," "Salesforce and HubSpot," "Datadog and New Relic") as if their presence were implied context. Use escape-hatch phrasing instead: "the other major [category] platforms," "[incumbent]-class tools," or "the dominant [category] incumbents." This applies in every section — Stage 2 concepts, Stage 4 SEO, Stage 5 competitor saturation, Stage 7 dialogue, Stage 8 earned-media targets. "Everyone in the industry knows it exists" is not a licence to name it.
After presenting the five concepts, ask the user to pick one (or more) to push through Stage 3–5.
Classify the user's spend asymmetry using the table in references/asymmetry-audit-table.md.
Report back one sentence: Your asymmetry is <level>. This means <what it means for your strategy>. Do not hedge. Do not offer a "balanced" recommendation if the user is at
categorical — it would be misleading.
Then run a Preconditions Check. The organic-first playbook wins when preconditions are
present; asymmetry alone is not enough. Score the user's situation against the six factors
that made the Hungarian case work (see references/hungarian-case-study.md for the full
mechanism). Ask or infer:
Score 0–6. Tell the user the count plainly and what it implies:
Before assembling a channel stack, verify the campaign is solving a distribution problem, not an MMF problem. Distribution amplifies signal; it cannot manufacture it. A founder's great LinkedIn post cannot sell a product nobody wants, and a movement's best volunteer network cannot turn out voters for a message that does not name their pain.
Ask the user three yes/no questions. Do not skip any. If the user does not know the answer to one, treat that as a "no" — absence of evidence is evidence of absence for MMF.
Scoring:
Report the MMF verdict at the top of the Stage 3 section of the final output so the user sees it before the channel stack.
Function before cost. Before picking channels, pick the campaign's primary function
against the user's bottleneck (from Stage 1 Q6). Use the function table at the top of
references/channel-tier-stack.md:
A mild-asymmetry user with a trust bottleneck should not be routed to paid amplification just because they can afford it. Route by function first; allocate within that function by cost/asymmetry second.
Apply the sector rider. After the function choice but before allocation, open
references/sector-riders.md and apply the rider matching the user's sector
(captured in Stage 1). The rider adjusts:
Do not overwrite the function-first choice. The rider layers on top. If the rider and the function choice conflict (e.g., B2B SaaS rider biases toward founder-LinkedIn but the function choice is demand capture), surface the conflict and name both paths rather than collapsing to one.
If the user picked "other" for sector, flag the mismatch in the Assumptions table and proceed with the closest rider — naming which of the rider's structural assumptions do not apply.
Then assemble the channel stack using references/channel-tier-stack.md. Allocation
rules layer on top of the function choice and the sector rider:
references/authenticity-playbook.md)
before reconsidering.Output the stack as a prioritized list with: (a) the primary function chosen, (b) the channels mapped to that function, (c) an estimated weekly effort commitment per channel, (d) the 70/30 (or 80/20) split in plain numbers.
Anti-fabrication carries through. The Stage 2 anti-fabrication rule applies to
every element of the Stage 4 output: SEO keyword examples, long-tail query lists,
directory/review-site references, competitor saturation descriptions, and any sample
copy shown inline with the stack. If the brief did not name the incumbent, the
incumbent's proper noun must not appear in this stage in any casing — not
title-case ("Sentry alternative"), not lowercase ("sentry alternative"), not
hyphenated, not as part of a compound keyword or URL. Search-query examples that
would otherwise require a brand name must either retain the [incumbent] bracketed
placeholder for the user to fill in, or be rewritten as non-brand equivalents
("error monitoring for small teams," "application monitoring under $100/seat",
"lightweight APM for node.js"). This applies equally to Stage 5's competitor
saturation map and Stage 6–10 content: the banned-token discipline does not
relax downstream of Stage 2.
Given the selected concept + channel stack, produce:
Competitor saturation map. Before shapes, before ad copy, before anything: for each of the top 2 named competitors (or top 2 competitor categories if the user did not name specific ones — see Principles), produce:
(a) What they saturate — the channels, visual style, message tropes, production value, and emotional register the competitor is flooding. Be specific: "paid-heavy LinkedIn carousels with stock illustrations and growth-hack CTAs," not "social media ads."
(b) The absence that becomes your signal. What is the competitor doing that your refusal to do becomes the positioning? Worked examples:
(c) One-sentence positioning line the user commits to holding across the campaign. This is the single sentence every piece of content must reinforce.
Three alternative campaign shapes for executing the concept, with tradeoffs. Examples
of shapes: community-first (start with 100 real people, grow through word of mouth),
earned-media-first (one newsworthy action drives press + organic amplification),
search-capture-first (dominate long-tail high-intent queries where demand already
exists). Use the alternative-generator pattern — do not collapse to one recommendation
prematurely; let the user choose. Each shape must include at least one flagship piece
of content structured as Self / Us / Now (Marshall Ganz's organizing framework —
see references/authenticity-playbook.md): the leader's lived experience, the shared
community reality, and the specific time-bound ask. If the user cannot tell their Self
story, drop the founder-led shape and route to community-first, earned-media-first, or
search-capture-first instead.
First-30-days action list — concrete weekly actions for weeks 1–4, mapped to the chosen shape. Each action has an owner (if multiple people), an effort estimate, and a clear success signal.
Capacity is a hard constraint. After drafting the week-by-week list, sum total weekly effort. If it exceeds the user's stated capacity (Stage 1 Q8, default 6h/week), cut the lowest-ROI actions until total effort fits inside the ceiling. Name the cuts explicitly: "I am cutting X and Y because the draft came to 14h/week and you said 6h/week. These are the actions to re-add if you can carve out more time later." Do not ship a plan the user cannot execute.
Earned-media actions must be specific or flagged. Every earned-media action in the list must include:
If the skill does not know specific targets in the user's niche (because the user did not name them and the skill cannot invent names — see Principles), assign target research as the week-1 action and set success criteria for the research itself (e.g., "produce a ranked list of 15 targets with RSS + contact channel by Friday").
Community-build is a multi-week sub-campaign, not a line item. If a Slack / Discord / WhatsApp / Circle community node is in the channel stack, it gets its own block in the first-30-days list, not one line at 1h/week:
Ad copy + boost rules — only if paid has a role in the chosen stack:
references/authenticity-playbook.md).references/channel-tier-stack.md).references/lift-test-templates.md) before continued spend.Lift-test / measurement plan — mandatory, no exceptions. One concrete experiment
using the templates in references/lift-test-templates.md. Template selection:
Anti-vanity metric dashboard — the short list of metrics the user should track and the longer list of metrics they should explicitly ignore. Examples:
Produce the final deliverable in this exact order so the user can scan it and act:
# Organic-First Campaign Plan — <user / project name>
## 0. Assumptions (required under Mode C — default mode; omit under Mode A/B)
<table: field → assumed value, flagging every default applied from Stage 1 so the user can confirm or adjust inline at the end>
## 1. Campaign Ideas (5+ concepts across archetypes)
<concepts with thesis, archetype, primary tier, authenticity hook, MVP>
## 2. Selected Concept
<the one (or more) the user picked>
## 3. Spend Asymmetry Verdict
<mild / severe / categorical, one sentence explaining what it means>
## 3a. Message-Market-Fit Gate
<3-question score, verdict (confirmed / borderline / failed), and — if borderline or failed — the validation cycle the user must run before proceeding>
## 4. Channel Tier Stack
<prioritized channel list with weekly effort>
## 5. 70/30 (or 80/20) Allocation
<organic % / paid %, with rationale>
## 6. Competitor Saturation Map
<per competitor: what they saturate, the absence that becomes your signal, one-sentence positioning line>
## 7. Three Alternative Campaign Shapes
<three shapes with tradeoffs>
## 8. First-30-Days Action List
<week 1–4 concrete actions, scaled to stated capacity with cuts named>
## 9. Ad Copy + Boost Rules (if paid applies)
<creative direction + 24–48h gate + frequency cap + refusal note if categorical>
## 10. Lift-Test / Measurement Plan
<one concrete experiment with threshold>
## 11. Anti-Vanity Metric Dashboard
<track list / ignore list>references/campaign-archetypes.md — 15+ archetypes the ideation engine draws from.references/asymmetry-audit-table.md — decision table for classifying spend asymmetry.references/channel-tier-stack.md — Tier 1–4 channels with 2025–2026 benchmark data.references/authenticity-playbook.md — founder voice, kitchen-table framing,
counter-positioning, narrative coherence.references/lift-test-templates.md — geo-holdout and conversion-lift experiment templates.references/sector-riders.md — six sector-specific overlays applied in Stage 4.references/hungarian-case-study.md — Tisza vs. Fidesz 2026 worked example.20077d3
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.