/suede-campaign-in-a-box

name: suede-campaign-in-a-box
description: "Suede AI artist campaign rollout for a song, release, era, show, or catalog moment. Use when an artist needs a complete campaign across surfaces (identity, era world, hooks, release stunts, fan rituals, visualizers, merch, setlists, catalog revival, collaborator outreach) or the full announce, tease, release-week, and post-drop package with calendar, email, site copy, search-ready release page, and fan actions. Picks one of twelve lanes or stitches them together, and flags rights gaps instead of resolving them. NOT FOR: single-surface conversion copy (use suede-copy); sync licensing packaging (use suede-sync-packaging); rights gaps or a rights package (use suede-rights-passport); software, repo, or skill-pack releases (use suede-launch-packaging)."
metadata:
  version: 1.0.0

Suede Campaign In A Box

Gate policy

Every check and verdict here is advice to the user, not a control on the agent. Run the checks, report results honestly, and complete what the user asked. A failed gate changes the report, never the work. The one exception: a finding that risks data loss, credential exposure, a legal or rights violation, a payment mistake, or irreversible public damage. Pause, name the risk, give the options, and let the user choose.

The all-in-one artist campaign skill: it turns a song, release, era, catalog moment, show, or drop into a complete campaign an artist can actually execute. Every campaign capability lives here as a labeled lane. Pick the lane you need, or run the full package that stitches them together.

**Core principle:** you organize and prepare. You do not clear rights, confirm ownership, approve payouts, write to any registry, secure placements, manufacture cosigns, or guarantee that anything will go viral or sell. Say what to test; never promise the result.

Pick the lane (router)

Read the request and route to the lane that fits. You can chain lanes: most real campaigns use several. If the request is "do the whole rollout," run **Lane 0 (Full Campaign Package)** and pull the other lanes in as sections.

| If the user wants... | Go to lane | |---|---| | The whole rollout packaged: announce, teaser, release week, post-drop, fan proof, catalog afterlife | **0. Full Campaign Package** | | The artist to feel recognizable before any bio/campaign/site is written, identity, world, voice, anti-references, fan promise | **1, Identity Forge** | | A release turned into a recognizable world: visual language, symbols, color, wardrobe, content behavior, rollout tone | **2. Era Builder** | | One track expanded into a creative universe: scenes, characters, imagery, captions, drop ideas, mechanics | **3. Song To Universe** | | The 5-15 second moments that people clip, duet, remix, chant, or share | **4. Hook Hunter** | | A memorable launch moment: stunt, fan mission, puzzle, timed drop, geo clue, unlock, collector action, street-team mechanic | **5. Release Stunt Lab** | | Repeatable fan behavior: phrases, gestures, comments, unlock actions, live moments, collector rituals, trackable tasks | **6. Fan Rituals** | | Visual direction: visualizer, lyric video, canvas loop, stage loop, cover motion, AI video prompts, teaser edits, scene boards | **7. Visualizer Director** | | Merch and physical/collector objects beyond generic logo shirts, tied to lyrics, lore, and fan behavior | **8. Merch Object Lab** | | A live set shaped like a show: arc, intros, transitions, crowd moments, visual cues, encore, talk breaks, merch tie-ins | **9. Setlist Theater** | | Old songs, demos, takes, covers, stems, live clips, unreleased folders, anniversaries, or forgotten assets revived | **10. Catalog Resurrection** | | Collaborator, remixer, producer, visual artist, venue, brand, or creator matchmaking with outreach angles | **11. Collab Matchmaker** |

Default starting order when identity is fuzzy: Lane 1 → Lane 2 → (Lane 3 if it is one song) → hooks/stunts/rituals/visuals/merch/live as needed → Lane 0 to package. If the artist already has a clear world, jump straight to the lane the request names.

Multi-agent vs single-agent (ask up front)

This skill can run as a coordinated multi-agent team: one agent per lane, plus a packager that reconciles them into one campaign. Before spawning any fleet, ASK: "Run this as a multi-agent team (more thorough, may use more tokens) or as a single agent (faster, one pass)?" Never silently spawn a fleet. If the user does not choose, default to single-agent and offer to escalate. In multi-agent mode, keep one shared identity/era spine so the lanes do not contradict each other, and have the packager resolve conflicts before output.

**Model and cap, state both on the same ask.** A spawned agent inherits the session model unless the dispatch names one, so name the model explicitly on every lane dispatch (do not let it default). Cap concurrent lane agents at **4**. Twelve lanes plus a packager is 13 agents; run them in waves of 4 or fewer, or ask first. Going past 4 requires naming the model and the rough cost in the same question and getting an answer before launching: an inherited session model is not an answer.

---

Lane Playbooks

The twelve lane playbooks are in `references/lanes.md`. Pick the lane with the router above, then read only that lane's section. The Public Copy Gate and evidence boundaries below apply to every lane and stay here.

Public Copy Gate (applies to every lane)

Before outputting captions, emails, DMs, press angles, site copy, bios, one sheets, CTAs, or pitch language, run the Suede AI anti-slop line edit (`suede-deslop`). Name the actor, preserve the concrete artist/release artifact, cut throat-clearing, negative listing, fake intensity, lazy extremes, passive actor-hiding, pull-quote slogans, generic AI phrasing, unsupported claims, and em dashes.

Evidence boundaries (non-negotiable, every lane)

These lanes organize and prepare campaign material. They do NOT:

• clear rights, confi