campaign-debrief
Skill6 starsChanged 4 months agoMITView on GitHub
Runs the post-campaign autopsy — goal vs actual, element-level diagnosis of what worked and what failed, keep or kill or change verdicts — and writes the portable lessons into marketing-brief.md. Use within a week of the campaign ending, while the evidence is warm.
In this repository29 other files it gives its agents.
- ad-scriptsSkill
- battlecardSkill
- brand-voiceSkill
- case-study-writerSkill
- channel-pickerSkill
- cmoSkill
- competitor-teardownSkill
- content-calendarSkill
- creative-briefSkill
- customer-deep-diveSkill
- email-sequenceSkill
- experiment-backlogSkill
- funnel-mapSkill
- hook-factorySkill
- kpi-treeSkill
- landing-pageSkill
- launch-planSkill
- lead-magnet-builderSkill
- marketing-auditSkill
- market-research-sprintSkill
- message-mapSkill
- objection-mapSkill
- offer-builderSkill
- onboardSkill
- positioning-workshopSkill
- pricing-testSkill
- repurposeSkill
- research-to-briefSkill
- weekly-reviewSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
Restate the pre-launch goal: If no goal was written down before launch, that is finding number one — reconstruct the honest intent and mark …
- Distinctive: line 32
No narrative rescue. "We built awareness" is what failure says when nobody set a goal.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Campaign Debrief — the autopsy that makes the next one cheaper
The most expensive part of a failed campaign is running the same failure again. The most expensive part of a winner is not knowing which element won. A campaign is a bundle — angle, audience, offer, creative, channel, timing — and only an element-level autopsy tells you what to carry forward and what to bury.
Inputs
- The campaign, its goal as set before launch, and every result available (spend, stage metrics, sales): $ARGUMENTS
- From
marketing-brief.mdif present: the plan or goal as recorded, numbers that matter (what a result is allowed to cost), and past learnings — so this debrief compounds on the last one instead of repeating it.
Do this
- Restate the pre-launch goal. If no goal was written down before launch, that is finding number one — reconstruct the honest intent and mark it as reconstructed.
- Goal vs actual, then the economics: the headline numbers side by side, then cost per result against what the brief says the business can afford. A campaign can hit its number and still be unaffordable.
- Break the bundle into elements: angle, audience and targeting, offer, creative format, hook, channel, landing step, timing. Attach each element's own evidence where it exists — hook rate, click-through, conversion per stage, replies.
- Diagnose element by element. Metric patterns point at elements. Where the data cannot isolate one, write "can't tell" — a guess recorded as a finding poisons the next campaign.
- Stopped but did not click — the creative promised weakly.
- Clicked but did not convert — the page or offer broke the promise.
- Converted but unaffordable — the targeting bought the wrong buyers.
- Bought but refunded — the offer promised what delivery could not keep.
- Rule keep, kill, or change per element, with one line of reasoning each.
- Extract 3–5 portable lessons — things true beyond this campaign ("this audience answers pain angles, ignores aspiration") — each citing its evidence. A lesson that only applies to this campaign is a footnote, not a lesson.
- Write it to
marketing-brief.md: the lessons and element verdicts into a dated Learnings & experiments section (create it if absent), plus any instrumentation gap that made "can't tell" verdicts necessary. The next campaign starts from here.
Output
The debrief one-pager: goal vs actual with the economics, the element table with verdicts and evidence, the portable lessons, and the single biggest thing to do differently next time. Lessons live in marketing-brief.md, not in a document nobody reopens.
Rules
- No narrative rescue. "We built awareness" is what failure says when nobody set a goal.
- Evidence over invention: every lesson cites its data. A lesson without evidence is an opinion in a lab coat.
- "Can't tell" is a legitimate verdict — record it and instrument better next time.
- Diagnose elements, not people. An autopsy that assigns blame stops being told the truth.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

