marketing-guide

Every playbook does the same setup and follows the same rules. They live here once.

Other skills. A playbook, its steps and these shared rules are separate skills that sit side by side. "The <slug> skill (../<slug>/SKILL.md)" names one: with files, read that path; in a chat app without files, fetch it from the GooseWorks catalog by its slug (gooseworks:catalog_fetch, type skill, slug <slug>; add path for a file inside it, such as references/<file>.md). The skills a playbook needs are listed as its dependencies and come with it.

1. Connect and pick the brand

1. Connected? If no gooseworks: tools are listed, call gooseworks:tools_load once for the group you need. Still none → a playbook with local mode says once "GooseWorks isn't connected, so I'll keep this brand's notes in this folder and you'll approve each change here." (no last clause if it changes nothing) and follows §5; any other says only "Connect GooseWorks first — I through it." and stops. Never half-run.
2. First GooseWorks call of the conversation: gooseworks:get_started with the marketer's own words. Its answer settles setup, and the brand only when the marketer named it; the playbook's gates decide the rest.
3. Which brand? gooseworks:brand_read lists the brands. One brand → use it. Several and none named → ask which, by name, before any research; never default to one. Keep the brand's coworker_agent_id.
4. Read the brain before asking anything. Ask only what the brain and the public site cannot answer.
   • Brain tools. The Brand Brain tools are brand_knowledge_browse, brand_knowledge_search, brand_knowledge_read and brand_knowledge_save. Their presence means the brain path (claims excepted: the claims-gate skill decides). Never request brand_read's sources section in a routine read: it can pass 100K characters.
   • When brand_knowledge_* tools are listed (the Brand Brain), start with gooseworks:brand_knowledge_browse: the rules, the never-list, the items waiting for the marketer's yes, and the chapters' "read when" hints. Open the chapters the task needs and its required_reads (brand_knowledge_browse kind or gooseworks:brand_knowledge_read); gooseworks:brand_knowledge_search for gaps.
   • Otherwise: gooseworks:brand_read (lean is enough for rules: every must and dont comes back), then gooseworks:knowledge_search for the task. Never every section at full detail in one call (it overflows and gets skipped); learnings at detail: "full" go in their own call.
   • Found vs confirmed. Only confirmed items are the brand's settled truth; found items (everything an agent saved) are context. Items waiting for a yes may go in drafts, labelled as waiting, never in public copy, claims or ads. Internal items (is_public: false) stay internal, even in drafts.
5. Repeatable playbooks: the Start steps of the run-memory skill (../run-memory/SKILL.md) before the playbook's own work, its End steps at the end.

2. Where files go