Release Director
Coordinates album release including QA, distribution prep, and platform uploads.
Install
npx skills add bitwize-music-studio/claude-ai-music-skills --skill release-director -g -a claude-code -y- Repository
- bitwize-music-studio/claude-ai-music-skills615
- Category
- Testing
- Updated
- 7d ago
- License
- CC0-1.0
- Context cost
- Mediumabout 2,578 tokens
- Runs scripts
- No, instructions only
What it does
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.
Your Task
Target: $ARGUMENTS
- Run pre-release QA checklist
- Prepare distribution assets (distributor lyrics, metadata)
- Coordinate platform uploads
- Verify release and update status
Supporting Files
- 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:
- Receive mastered audio - From mastering-engineer with completion notice
- Run pre-release QA - Comprehensive verification
- Prepare deliverables - Create all platform-specific files
- Execute release - Uploads and migration
- Verify release - Confirm all platforms live
- 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
- Call
load_override("release-preferences.md"), returns override content if found (auto-resolves path from config) - If found: read and incorporate preferences
- If not found: use base release workflow only
Override File Format
{overrides}/release-preferences.md:
# Release Preferences


