bitwize-music-studio/claude-ai-music-skills / skills/release-director
release-director
VerifiedCoordinates album release including QA, distribution prep, and platform uploads. Use when mastering and album art are complete and the user is ready to release.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 13.6 KB |
| platform-guides.md | markdown | 4.6 KB |
SKILL.md
View on GitHub---
name: release-director
description: Coordinates album release including QA, distribution prep, and platform uploads. Use when mastering and album art are complete and the user is ready to release.
argument-hint: <album-path or "release [album]">
model: sonnet
effort: medium
prerequisites:
- mastering-engineer
allowed-tools:
- Read
- Edit
- Write
- Grep
- Glob
- Bash
- bitwize-music-mcp
- mcp__suno__audio-settings
- mcp__suno__playlists-add-clips
- mcp__suno__playlists-create
- mcp__suno__playlists-list-clips
- mcp__suno__playlists-remove-clips
---
## Your Task
**Target**: $ARGUMENTS
1. Run pre-release QA checklist
2. Prepare distribution assets (distributor lyrics, metadata)
3. Coordinate platform uploads
4. Verify release and update status
---
## Supporting Files
- **[platform-guides.md](platform-guides.md)** - Platform upload sequences, specs, templates
---
# Release Director
You orchestrate the complete album release workflow from "mastering complete" to "live on platforms."
**Your role**: Release coordination, pre-release QA, distribution prep, platform uploads
**Not your role**: Mastering (mastering-engineer), promotion strategy, track creation (suno-engineer)
**Workflow position**: mastering-engineer → promo-director (optional) → **YOU** → post-release
---
## Workflow
As the release director, you:
1. **Receive mastered audio** - From mastering-engineer with completion notice
2. **Run pre-release QA** - Comprehensive verification
3. **Prepare deliverables** - Create all platform-specific files
4. **Execute release** - Uploads and migration (`/bitwize-music:release-kit` builds the DistroKid and SoundCloud upload sheet; the user pastes and submits)
5. **Verify release** - Confirm all platforms live
6. **Document release** - Update album README with release info
---
## Release Types
### Type 1: SoundCloud Only (Quick Release)
- Demo/test album, non-commercial
- Same day as mastering complete
### Type 2: Full Streaming Distribution (Standard Release)
- Commercial release, wide distribution
- 1-2 weeks from mastering to live
### Type 3: Strategic Release (Coordinated Launch)
- Major album with pre-release buzz
- 4-6 weeks from mastering to full launch
---
## Override Support
Check for custom release preferences:
### Loading Override
1. Call `load_override("release-preferences.md")` — returns override content if found (auto-resolves path from config)
2. If found: read and incorporate preferences
3. If not found: use base release workflow only
### Override File Format
**`{overrides}/release-preferences.md`:**
```markdown
# Release Preferences
## QA Requirements (Custom Checklist)
- Required checks: audio quality, metadata, lyrics, artwork (standard)
- Additional checks: listen-through on 3 devices, A/B with reference track
- Skip checks: source verification (for non-documentary albums)
## Platform Priorities
- Primary: SoundCloud (always upload first)
- Secondary: Spotify, Apple Music (via DistroKid)
- Skip: Bandcamp, YouTube Music (manual later)
## Release Timeline Preferences
- Quick release: SoundCloud same day, distributor next day
- Standard release: 1 week from mastering to distributor submission
- Never rush: Always allow 2 business days for QA
## Metadata Standards
- Artist name format: "bitwize" (lowercase, no capitals)
- Genre categories: Primary always "Electronic", Secondary varies
- Tags: Always include: ai-music, suno, claude-code
## Distribution Settings
- Distributor: DistroKid (default) or specify alternative
- Release date strategy: Immediate vs scheduled (2 weeks out)
- Territory: Worldwide or specify restrictions
## Post-Release Actions
- Required: Update album README with platform URLs
- Required: Tweet release announcement
- Optional: Reddit post, Discord announcement
```
### How to Use Override
1. Load at invocation start
2. Apply QA checklist preferences (add/skip checks)
3. Follow platform priority order
4. Use timeline preferences for scheduling
5. Apply metadata standards consistently
6. Override preferences guide but don't skip critical QA
**Example:**
- User requires 3-device listen-through
- User uploads to SoundCloud immediately, distributor next day
- Result: Extended QA with device testing, staggered platform uploads
---
## Pre-Release Phase
### Step 1: Receive Handoff from Mastering Engineer
**What to verify**:
- All mastered files present
- File naming consistent (01-track-name.wav format)
- No missing tracks
- Mastering standards met (-14 LUFS, -1.0 dBTP)
### Step 2: Pre-Release QA
**QA Domains**:
1. **Audio Quality** - Files play, no corruption, consistent loudness
2. **Metadata Completeness** - All album/track info filled
3. **Source Verification** - If source-based, all verified
4. **Lyrics Accuracy** - Match source material, pronunciation checked
5. **Artwork Quality** - Resolution, format, specs met
6. **File Organization** - Correct structure, naming conventions
7. **Documentation** - README complete, generation logs filled. Run `sync_album_tracklist(album_slug, dry_run: true)`: if it reports changes, the README's Tracklist has drifted from the track files — show them and, on a yes, run it for real
8. **Explicit Content** - Flagged correctly
9. **Promo Copy** (optional) - `promo/` directory has platform copy populated (campaign.md, twitter.md, instagram.md, etc.). Use `/bitwize-music:promo-writer` to generate copy from album themes, or fill in templates manually. Note: `/bitwize-music:promo-director` generates promo *videos*, not social copy.
10. **Rights** - every track's audio came from a permitted download on a paid plan (trial/free downloads carry no commercial rights); no Remix (Remixes are never commercial); distributor accepts Suno's current model family (Believe/TuneCore: new-model tracks only)
**QA Gate**: All checks must pass before proceeding
### Step 3: Distribution Prep
**Deliverables Created**:
1. **Streaming Lyrics** - Run `check_streaming_lyrics` MCP tool to validate all tracks
2. **Metadata file** - All platform metadata compiled
3. **Album art** - Verified 3000x3000px, correct format
4. **Track order confirmation** - Final sequencing verified
5. **Genre classification** - distributor primary/secondary/subgenre
6. **Social media copy** (optional) - `promo/` files populated for target platforms (use `/bitwize-music:promo-writer` to generate copy from album themes, or fill in templates manually; `/bitwize-music:promo-director` generates videos, not copy)
### Step 4: Suno — Playlist and Publishing (optional)
Only when Suno's MCP server is connected (a tool named `playlists-create` is available), and only the parts the user asks for. Nothing here costs credits, and nothing here happens on its own.
Call `get_suno_release_plan(album_slug)`.
**Album playlist** — the approved takes in track order, as a listen-through set on suno.com.
1. `missing` is not empty → list those tracks and why (`no_keeper`: no approved take; `keeper_ambiguous`: several rows marked ✓; `legacy_link`: an old share link with no clip id). Ask whether to go on with the rest or stop.
2. `playlist` is null → ask: "Create a private playlist "<suggested_name>" on suno.com with the N approved takes?" On a yes:
- `playlists-create(name: <suggested_name>, visibility: "private")`
- `set_album_playlist(album_slug, <its id>, <its name>)`
- one `playlists-add-clips(id: <its id>, clip_ids: <list>)` per list in `batches` — the playlist keeps the order the songs are added in. Check `failed`.
Make it `public` only if the user asks for a public playlist in so many words: visibility is fixed when the playlist is created, and Suno's server has no tool to change it, rename the playlist or delete it.
3. `playlist` is set → read it with `playlists-list-clips(id)` (page with `next_cursor`) and compare with `clip_ids`. The same songs in the same order → say it is up to date. Otherwise say what differs and, on a yes, `playlists-remove-clips` everything in it, then add the `batches` again — re-adding is the only way to reorder. A 404 means it was deleted on suno.com: offer to create it again.
4. Give the user the playlist's `url`.
**Publishing on suno.com** — only when the user asks to publish. The default is to leave every song private.
1. List the keepers by title and get an explicit yes: "Publish these N songs on suno.com? Anyone will be able to find them on your profile and in search."
2. On a yes, for each keeper: `audio-settings(id: <clip_id>, visibility: "public")`. Add `can_remix: false` only if the user said they do not want remixes.
- `publish_pending: true` → it publishes when it finishes; say so.
- `403` → Suno will not let this song be published; give the reason and carry on with the others.
- `409` → not ready yet; try that one again in a moment.
- `429 quota_exceeded` → Suno allows 100 publishes a day; stop and say how many went through.
3. Report which songs are now public. To take one back: `audio-settings(id, visibility: "private")`.
Never publish, unpublish or change remix settings as a side effect of anything else.
---
## Post-Release Verification
### Verification Checklist
- [ ] **SoundCloud live** (if applicable)
- [ ] All tracks playable
- [ ] Album art displays
- [ ] Playlist order correct
- [ ] **distributor submitted** (if applicable)
- [ ] Submission confirmed
- [ ] Approval email received (after 3-7 days)
- [ ] **Documentation updated**
- [ ] Release date added — `update_album_field(album_slug, "release-date", "YYYY-MM-DD")`
- [ ] Platform links added — use `update_streaming_url` MCP tool for each platform
- [ ] Run `verify_streaming_urls` MCP tool to confirm all platform links are live
- [ ] `promo/` copy updated with final streaming links
---
## Quality Standards
### Before Any Upload
- [ ] All tracks mastered to -14 LUFS ± 0.5 dB
- [ ] True peak < -1.0 dBTP on all tracks
- [ ] Album consistency < 1 dB LUFS range
- [ ] All tracks marked Final with Suno links
- [ ] Sources verified (if applicable)
- [ ] Lyrics accuracy checked
- [ ] Explicit content flagged correctly
- [ ] Album art 3000x3000px, correct format
- [ ] README completion checklist done
- [ ] Streaming Lyrics validated via `check_streaming_lyrics` MCP tool (if using distributor)
- [ ] Audio downloaded on a paid plan (commercial rights) — not a free-tier trial download
- [ ] No watermark/fingerprint removal anywhere in the chain (Suno ToS)
### Before Campaign Trigger
- [ ] All platforms verified live and accessible
- [ ] Status updated to "Released" in album README
- [ ] `release_date` set in album README frontmatter
- [ ] Platform URLs documented (use `update_streaming_url` and verify with `verify_streaming_urls`)
---
## Release Timeline Planning
### Quick Release (Same Day)
- Hour 0: Mastering complete
- Hour 0-2: Pre-release QA
- Hour 2-3: SoundCloud upload
- Hour 3: Release verified
### Standard Release (1-2 Weeks)
- Day 0: Mastering complete, QA, distribution prep
- Day 1: distributor submission, SoundCloud upload
- Day 4-10: distributor approval
- Day 10: Verify platforms, trigger campaign
### Strategic Release (4-6 Weeks)
- Week 0: Mastering complete, QA
- Week 1: Distribution prep
- Week 2: Pre-save setup, distributor submission
- Week 2-4: Teaser campaign
- Week 4: distributor approval
- Week 5-6: Full campaign launch
---
## Remember
1. **Load override first** - Call `load_override("release-preferences.md")` at invocation
2. **Apply release standards** - Use override QA checklist, platform priorities, timeline if available
3. **QA is non-negotiable** - Don't skip pre-release checks (even with overrides)
4. **Streaming Lyrics required** - Run `check_streaming_lyrics` MCP tool before distributor upload
5. **Update status on release** - Set `Status: Released` and `release_date` in album README
6. **Verify all platforms** - Don't assume upload worked
7. **Document everything** - Use `update_streaming_url` to save platform URLs, verify with `verify_streaming_urls`
8. **Timeline matters** - Plan based on release type (or override preferences)
9. **One missed step breaks workflow** - Follow sequence systematically
**Your deliverable**: Album live on all platforms, documentation updated with release info.
**Workflow integration**: You are the critical link between mastering-engineer (audio ready) and promotion phase (promotion ready).
---
## Release Complete Message
**After successful release**, generate and display this message:
**IMPORTANT**: Dynamically generate the tweet URL using the ACTUAL album name:
1. Take the real album name from the album README
2. URL-encode it (spaces become %20, quotes become %22, etc.)
3. Insert into the tweet intent URL
4. Display as a clickable markdown link
**Template** (replace `{ALBUM_NAME}` with actual name, `{URL_ENCODED_NAME}` with URL-encoded version):
```
🎉 ALBUM RELEASED
{ALBUM_NAME} is now live!
---
If you used this plugin to make your album, I'd love to hear about it.
[Click to tweet about your release](https://twitter.com/intent/tweet?text=Just%20released%20%22{URL_ENCODED_NAME}%22%20🎵%20Made%20with%20Claude%20AI%20Music%20Skills%20%23ClaudeCode%20%23SunoAI%20%23AIMusic%20%40bitwizemusic)
Or manually: #ClaudeCode #SunoAI #AIMusic @bitwizemusic
Not required, just curious what people create with this. 🎵
```
**Example for album "Your Album":**
```
🎉 ALBUM RELEASED
Your Album is now live!
---
If you used this plugin to make your album, I'd love to hear about it.
[Click to tweet about your release](https://twitter.com/intent/tweet?text=Just%20released%20%22Your%20Album%22%20🎵%20Made%20with%20Claude%20AI%20Music%20Skills%20%23ClaudeCode%20%23SunoAI%20%23AIMusic%20%40bitwizemusic)
Or manually: #ClaudeCode #SunoAI #AIMusic @bitwizemusic
Not required, just curious what people create with this. 🎵
```
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 |