From builder-growth
Use before any campaign moves from strategy to execution. Transforms a growth strategy and offer into an executable brief — campaign objective, audience, offer, message, channel, creative requirements, landing destination, CTA, success metric, review gates, and launch checklist. Blocks "the team knows what we're going for" completions.
How this skill is triggered — by the user, by Claude, or both
Slash command
/builder-growth:campaign-brief-generatorThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
```
A CAMPAIGN WITHOUT A BRIEF IS EXECUTED FROM MEMORY, AND MEMORY DIVERGES PER PERSON.
"The team knows what we're going for" means the copywriter, the designer, and the media buyer are each executing their own interpretation of a conversation, and the gaps between those interpretations show up as a campaign with three competing messages.
Objective + audience + offer + message + channel + creative requirements + landing destination + CTA + success metric + review gates + checklist IS an executable brief.
Trigger before:
growth-strategy-design, channel-selection-audit, and offer-quality-gate have already produced their outputs and the work is ready to become an executable campaignA complete brief defines all eleven. A brief missing any one leaves a decision to be made independently by whoever executes that part of the campaign.
The single result this campaign is meant to produce, tied to a growth-metrics-design output metric. One objective — a campaign briefed for "awareness and conversions and retention" gets executed as three different campaigns by three different people.
The specific segment this campaign speaks to — from the strategy, possibly narrowed for this specific campaign.
The validated offer from offer-quality-gate this campaign promotes. The brief does not redefine the offer — it references it.
The core message in one sentence, derived from the offer's promised outcome and validated by positioning-audit and copy-quality-gate before the brief is finalised.
The channel(s) this campaign runs on, from channel-selection-audit, with channel-specific format requirements (e.g., a paid social campaign needs different asset dimensions than an email sequence).
The specific assets needed: formats, dimensions, length limits, brand constraints, required elements (logo, disclaimer, CTA button). Specific enough that a designer or copywriter does not have to guess.
Where the campaign sends traffic, and what that destination must contain to deliver on the campaign's message (message match between ad and landing page is required, not optional).
The single action the campaign drives toward — matching the offer's CTA, not a different one invented for this channel.
The specific metric and target this campaign is evaluated against, from growth-metrics-design. Not "see how it does" — a number with a baseline.
The checkpoints before launch where the campaign is reviewed against builder-growth skill gates: positioning, copy quality, AI messaging (if applicable), social proof, and pricing (if applicable).
The final pre-launch checklist: assets approved, tracking instrumented, landing page live and tested, budget approved, stakeholders notified.
One objective, tied to a named output metric.
Reference the strategy and offer documents directly — do not redefine them in the brief.
One sentence. Run it through positioning-audit and copy-quality-gate if not already validated.
Pull from channel-selection-audit. Specify exact format requirements per channel.
List every asset needed with specs precise enough to execute without follow-up questions.
Verify message match between the campaign and the destination. If the destination doesn't exist yet or doesn't match, flag it as a blocker.
Match it to the offer's single CTA.
Pull from growth-metrics-design, with baseline and target.
List which skill gates this campaign must pass before launch, and when each review happens in the timeline.
Final pre-launch items, each with an owner.
Store at growth/campaigns/<campaign>-brief-<date>.md.
These thoughts mean the brief was not written — stop:
growth-metrics-design: a metric defined after the results come in is chosen to match whatever happenedWhen campaign-brief-generator is satisfied, state it like this:
Campaign brief complete.
File: growth/campaigns/<campaign>-brief-<date>.md ✓
Objective: [single result] — tied to metric: [output metric] ✓
Audience: [segment] ✓
Offer: [offer, from offer-quality-gate] ✓
Message: "[one sentence]" — positioning-audit ✓ / copy-quality-gate ✓
Channel: [channel(s), from channel-selection-audit] ✓
Creative requirements: <N assets> — specs defined ✓
Landing destination: [URL/page] — message match confirmed ✓
CTA: [single action, matches offer] ✓
Success metric: [metric] — baseline: <X>, target: <Y> ✓
Review gates scheduled: [positioning-audit / copy-quality-gate / ai-messaging-review / social-proof-review / pricing-page-review — as applicable] ✓
Launch checklist: <N items> — all owned ✓
A brief with no success metric or no scheduled review gates fails this gate.
The gap between a growth strategy and a shipped campaign is where most of the actual divergence happens — not because the strategy was wrong, but because the people executing it each filled the gaps in the brief with their own assumptions. A complete brief removes the gaps before execution starts, so the campaign that ships is the campaign that was strategized, not a committee's average interpretation of a hallway conversation.
npx claudepluginhub rbraga01/a-team --plugin builder-growthGuides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Enforces test-driven development: write failing test first, then minimal code to pass. Use when implementing features or bugfixes.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.