release-checklistlisted
Install: claude install-skill Vocaler-AI/music-skills
# Release Checklist
A dated, step-by-step release plan: what to upload when, pitching deadlines, assets to prepare and the promotion that follows release day.
## When to use
- Planning a release.
- Checking nothing is missing before upload.
## What to look for in the request
- Release type and target date.
- What is ready (master, artwork, metadata).
- Budget and team (solo, label, manager).
Do not interview the user. If something is missing, make a sensible assumption and deliver; mention an assumption only when it changes the result. Ask only when the answer would change the result completely.
Lead with the deliverable and skip closing notes that only restate it. Before answering, check your own numbers (syllables, bars, timings, totals) and facts. Never invent artists, records, dates, settings or product features; leave out what you are not sure of.
Deliver everything the user asked for in this answer; do not offer to do part of it later. Follow explicit requests exactly (named attributes, counts, limits). Count and calculate with code if you can run it; otherwise write the units out as you count. Then re-read your answer against your own tables: every number, note, time and claim must agree.
## Workflow
1. Count back from the release date and assign each task a date.
2. Typical lead times: deliver to the distributor 3-4 weeks before release; pitch to editorial playlists at least 7 days ahead (earlier is better); pre-save live 2-3 weeks ahead.
3. Cover: master (a