gooseworks-ai/goose-skills / skills/marketing/plan-campaign-channel-decision
plan-campaign-channel-decision
VerifiedStep of the plan-campaign playbook: marks each candidate channel Run, Test, Later or No with a brand-fact reason and founder hours. Run plan-campaign instead; not for direct use.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.9 KB |
| skill.meta.json | config | 236 B |
SKILL.md
View on GitHub---
name: plan-campaign-channel-decision
description: >-
Step of the plan-campaign playbook: marks each candidate channel Run, Test, Later or No with a
brand-fact reason and founder hours. Run plan-campaign instead; not for direct use.
version: 0.1.2
---
# Channel decision (atom)
**Load:** `../plan-campaign/references/channel-decision.md`.
**Inputs:** brand type and distribution footprint (where the product is sold); buyer groups and demand read (`research/audience/buyer-groups.md`, `research/market/demand.md`); landscape and where competitors invest (`research/competitors/landscape.md`, competitor files, `competitor_read` roster); the economics box and per-leg minimums; creative capacity (which makers and how much volume; past creative in `ads_creative_read`); tracking state; email list size; learnings log; the founder's hours; channels already committed or off-limits; existing campaign concepts (`campaign_read`).
**Do:**
1. Write every mandatory row, then the rows live for this brand type; one line "not relevant: <reason>" for conditional rows that are not.
2. For each row answer the seven lenses in your head; write the **deciding** reason in plain words with a brand fact, the evidence, how sure you are in words, and, unless kept, what would change it.
3. Prefer one or two channels done properly. A judgment-only Run becomes a Test. Novelty is never a reason. No default channel.
4. Mark execution per leg: GooseWorks levers (Meta objects it creates or pushes into) or written instructions / human hands. Add founder hours per leg; if the total exceeds what the founder has, cut a leg and say which.
5. Zero paid is allowed: state it in the paid rows with the numbers.
**Output:** the brief's `### Channel decisions` section and founder-hours line.
**Never:** a row without a brand-fact reason; "doesn't fit our audience" without saying who the audience is and where they are.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |