recoup-release-campaign
ARTIFACT: a dated rollout SCHEDULE (pre-release → release-week → post-release timeline with channels, assets, owners, dates counted back from the release date). Use for "plan the rollout for [single/EP/album]", "build a release campaign", "what's the schedule for release week", "give me a pre-release plan". This is one of three release skills — for CREATIVE DIRECTIONS use recoup-release-marketing-brief; for the master DOC + DSP pitch use recoup-release-doc; this one is the SCHEDULE. For "where do I even start" use recoup-release-start; for copy tone use recoup-brand-voice-caption.
What this skill does
# Recoup Release Campaign
Build an executable, dated marketing campaign for a music release. The output is
a timeline a human can run, not a vibe — every line has a date (or relative
offset), a channel, an asset, and an owner.
## Required inputs
- **Artist** and **release** (title, format: single / EP / album / video).
- **Release date** (or "TBD" — then plan in relative offsets).
- **Goal metric** (streams, saves, playlist adds, ticket sales, press).
- **Channels available** (IG, TikTok, X, YouTube, email list, DSP pitching,
press/PR) and whether there's paid budget.
Ask for any of these that are missing before producing the timeline. Never
invent performance numbers, playlist placements, or press commitments.
## Workflow
1. **Anchor on the release date — compute dates deterministically, don't do the
math by hand:**
```text
python3 scripts/build_campaign_timeline.py --release-date {YYYY-MM-DD|TBD} --type {type}
```
This returns every milestone as an offset (`R-21`, `R+7`) *and* its exact
calendar date, plus timing warnings (e.g. the ~28-day DSP editorial window).
Build your plan on those dates. (Script ships with this skill.)
2. **Build the three phases:**
- **Pre-release (≈ R-28 → R-1):** announce, build anticipation, secure DSP
pitch (note the ~4-week lead editorial playlists need), tease clips, open
pre-save, line up press/feature placements.
- **Release week (R-0 → R+6):** drop-day push across all channels, pin the
pre-save→stream conversion, coordinate artist posting, send the email blast,
activate any paid support, capture day-one reactions.
- **Post-release (R+7 → R+28):** sustain with follow-up content, chase
playlist/press momentum, repurpose top-performing clips, report results
against the goal metric.
3. **For each milestone, specify:** date/offset · channel · asset needed · owner
· the one outcome it drives.
4. **List the asset checklist** the campaign depends on (cover art, vertical
clips, lyric/visualizer, EPK/one-sheet, pre-save link, email copy) and flag
which are missing.
5. **Close with a measurement plan:** what to check at R+7 and R+28 against the
stated goal metric, and the trigger for doubling down vs cutting.
## Output format
A phase-grouped table or checklist (offset → action → channel → asset → owner),
followed by the asset checklist and the measurement plan. Keep it scannable.
When run inside a release workspace, save to
`releases/{artist-slug}/{release-slug}/campaign/campaign-$(date +%F).md`
(the `campaign/` folder of the shared workspace). Re-running the same day is a
no-op.
## Edge cases
- **DSP editorial lead time:** if the release is under ~3 weeks out, flag that
the pitch window for editorial playlists is tight or closed.
- **No paid budget:** weight the plan toward organic + artist-driven content and
say so; don't assume ad spend.
- **Catalog / re-release:** lean on the existing audience and anniversary hooks
rather than a "new artist" discovery push.
## Quality bar
The #1 failure mode is a **timeline with no owners or no dates** — that's a wish
list, not a campaign. Every line is actionable and assigned. If the user can't
hand a row to a person and have them execute it, tighten it.
## When to escalate
If the campaign needs historical data or fan insights you don't have, ask for
them or mark the gap. If the request is broader than one release (full artist
strategy), route back to `recoup-release-start`.
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".