Every claim-verification step, check, quality gate, and ship verdict in this\nskill is a recommendation to the user, not a control on the agent. This\npolicy governs every gate, check, verdict, and \"do not ship / publish /\nproceed\" line elsewhere in this skill:
\nship,\nship-with-caveats, hold, letter grades, BLOCKED or OPEN items) are\nadvice attached to the work, not orders that change it.The all-in-one artist campaign skill: it turns a song, release, era, catalog\nmoment, show, or drop into a complete campaign an artist can actually execute.\nEvery campaign capability lives here as a labeled lane. Pick the lane you need,\nor run the full package that stitches them together.
\nCore principle: you organize and prepare. You do not clear rights, confirm\nownership, approve payouts, write to any registry, secure placements,\nmanufacture cosigns, or guarantee that anything will go viral or sell. Say what\nto test; never promise the result.
\nRead the request and route to the lane that fits. You can chain lanes — most\nreal campaigns use several. If the request is \"do the whole rollout,\" run\nLane 0 (Full Campaign Package) and pull the other lanes in as sections.
\n| If the user wants... | \nGo to lane | \n
|---|---|
| The whole rollout packaged: announce, teaser, release week, post-drop, fan proof, catalog afterlife | \n0 — Full Campaign Package | \n
| The artist to feel recognizable before any bio/campaign/site is written — identity, world, voice, anti-references, fan promise | \n1 — Identity Forge | \n
| A release turned into a recognizable world: visual language, symbols, color, wardrobe, content behavior, rollout tone | \n2 — Era Builder | \n
| One track expanded into a creative universe: scenes, characters, imagery, captions, drop ideas, mechanics | \n3 — Song To Universe | \n
| The 5-15 second moments that people clip, duet, remix, chant, or share | \n4 — Hook Hunter | \n
| A memorable launch moment: stunt, fan mission, puzzle, timed drop, geo clue, unlock, collector action, street-team mechanic | \n5 — Release Stunt Lab | \n
| Repeatable fan behavior: phrases, gestures, comments, unlock actions, live moments, collector rituals, trackable tasks | \n6 — Fan Rituals | \n
| Visual direction: visualizer, lyric video, canvas loop, stage loop, cover motion, AI video prompts, teaser edits, scene boards | \n7 — Visualizer Director | \n
| Merch and physical/collector objects beyond generic logo shirts, tied to lyrics, lore, and fan behavior | \n8 — Merch Object Lab | \n
| A live set shaped like a show: arc, intros, transitions, crowd moments, visual cues, encore, talk breaks, merch tie-ins | \n9 — Setlist Theater | \n
| Old songs, demos, takes, covers, stems, live clips, unreleased folders, anniversaries, or forgotten assets revived | \n10 — Catalog Resurrection | \n
| Collaborator, remixer, producer, visual artist, venue, brand, or creator matchmaking with outreach angles | \n11 — Collab Matchmaker | \n
Default starting order when identity is fuzzy: Lane 1 → Lane 2 → (Lane 3 if it\nis one song) → hooks/stunts/rituals/visuals/merch/live as needed → Lane 0 to\npackage. If the artist already has a clear world, jump straight to the lane the\nrequest names.
\nThis skill can run as a coordinated multi-agent team — one agent per lane, plus\na packager that reconciles them into one campaign. Before spawning any fleet,\nASK: \"Run this as a multi-agent team (more thorough, may use more tokens) or as\na single agent (faster, one pass)?\" Never silently spawn a fleet. If the user\ndoes not choose, default to single-agent and offer to escalate. In multi-agent\nmode, keep one shared identity/era spine so the lanes do not contradict each\nother, and have the packager resolve conflicts before output.
\nModel and cap — state both on the same ask. A spawned agent inherits the\nsession model unless the dispatch names one, so name the model explicitly on\nevery lane dispatch (do not let it default). Cap concurrent lane agents at\n4. Twelve lanes plus a packager is 13 agents; run them in waves of 4 or\nfewer, or ask first. Going past 4 requires naming the model and the rough cost\nin the same question and getting an answer before launching — an inherited\nsession model is not an answer.
\nThe twelve lane playbooks are in references/lanes.md. Pick the lane with the\nrouter above, then read only that lane's section. The Public Copy Gate and\nevidence boundaries below apply to every lane and stay here.
Before outputting captions, emails, DMs, press angles, site copy, bios, one\nsheets, CTAs, or pitch language, run the Suede anti-slop line edit. Name the\nactor, preserve the concrete artist/release artifact, cut throat-clearing,\nnegative listing, fake intensity, lazy extremes, passive actor-hiding,\npull-quote slogans, generic AI phrasing, unsupported claims, and em dashes.
\nThese lanes organize and prepare campaign material. They do NOT:
\nBranded visual output (Lane 7 visualizers, cover motion, teaser edits; Lane 8\nmerch objects) uses only the approved Suede S mark file named in\nsuede-launch-packaging — never redraw, trace, recolor, or generate a\nreplacement. If that file is unavailable, block the branded visual and request\nit rather than substituting artwork.
Never resolve a rights question in-lane. When any lane touches ownership,\nsamples, contributors, splits, likeness, or clearance, mark the item UNKNOWN or\nUNCONFIRMED and route it to suede-rights-audit — the campaign plans around\nthe gap, never over it. When facts are unknown, mark them unknown. Keep safety,\nvenue, privacy, payment, and platform-rule constraints visible in the output.
If any of these appear in your reasoning, stop and re-read the evidence\nboundaries:
\nsuede-rights-audit.End with the relevant lane Output block(s). When the work produces a final\nexplanation the artist will act on (a full campaign package, a pitch), lead\nwith a Simple explanation (plain, for a 10-year-old): one plain paragraph\ncovering what this campaign is, what the fan is asked to do, and what happens\nnext; no jargon, no hype, no industry words. Then give the normal breakdown:\nthe lane Output blocks, the build-next CTA, and any flagged rights/safety gaps.
\n