agentleFS
gooseworks-aigooseworks-ai/goose-skills/skills/marketing/plan-campaign-brief-and-assets/SKILL.md

plan-campaign-brief-and-assets

Skill1.3k starsChanged 23 days agoMITView on GitHub

Step of the plan-campaign playbook: writes angles per channel, the asset list, measurement plan, hand-offs and replan triggers, then assembles the plan. Run plan-campaign instead; not for direct use.

1 other project uses a version of this.

Trending

More talk lately.about the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 1 mentionJun 2026: 0 mentionsJul 2026: 2 mentionsAug 2026: 1 mentionSep 2026: 0 mentionsOct 2026: 15 mentionsNov 2026: 1 mention
Dec 2025Jun 2026Nov 2026
Mentions a month of the gooseworks-ai/goose-skills repository that our weekly crawl found. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about gooseworks-ai/goose-skills

The biggest 5 of 20 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 20

Talked about on GitHub (20 times).

On GitHub · 20

15 more on GitHub

The file

Files
SKILL.md

Brief and asset list (atom)

Load: ../plan-campaign/references/brief-template.md, ../plan-campaign/references/launch-and-calendar.md, the write-report skill (../write-report/SKILL.md) (§1 writing rules, §3 check).

Inputs: all earlier sections; approved claims = the claims that are usable through the claims-gate skill (../claims-gate/SKILL.md) ("Claims sign-off" marker, "Claims you may use" must facts, dated Brand record; or confirmed brain claims), with server applicability from knowledge_search ["claim"] + product_id; the angle bank and voc bank files (research/competitors/angle-bank.md, research/audience/voc-bank.md); existing campaign concepts; the brand voice from the kit.

Do:

  1. Angles per Run/Test channel: one reason to buy each, resting on a named customer line and an exact approved claim (with id) whose applicability covers it (brand, or product for that product). unknown applicability is not brand-wide proof — the server refuses it on a concept; mark needs proof (scope unconfirmed). Adapt the expression per channel. No approved proof → needs proof, never invented. Press quotes and the brand's own site copy are not customer words; if research-market's voice-of-customer bank is empty, say so.
  2. Asset list: one numbered row per asset — leg, placement, spec (format, ratio, length), angle, message/hook, claim (verbatim), CTA → destination (with UTMs), producer role (static ads, video ads, photos, content, human; video ads and photos are made with the goose-video and goose-product-photos skills, or by a person in local mode — the hand-off roles in ../plan-campaign/references/brief-template.md), due date (from the backwards calendar), dependency. Check the count against each paid leg's creative-volume need.
  3. Measurement plan per leg: conversion event, UTM convention, promo code, attribution window, the store/CRM number it is judged on, blended MER target, "how did you hear" question.
  4. Hand-offs: one row per leg, no silent legs; legs with no playbook are marked human-executed.
  5. Replan triggers with thresholds and the action each starts.
  6. Assemble the plan with the exact headings of the template, In short first; each section opens with its point in one sentence; plain words; no ids, codes, paths, tool or playbook names; every outside fact with its source and date. Fill every section or write "none — <reason>". Then run write-report §3's check.

Output: the full brief_md text and the concept list (person, message, proof, evidence, confidence, product_id) for the write-back.

Never: a claim the claims gate does not allow; an asset with no owner or date.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.