Manage music releases using RELEASE.md documents stored in releases/{release-slug}/ within an artist workspace. Triggers when the user mentions an artist's album, EP, single, or project — or asks about release planning, DSP pitches, metadata, marketing, press materials, physical production, or tour coordination. First infer which artist and release the user means, then find or create the RELEASE.md. Use this skill to create, update, or pull data from release documents, and to generate deliverables like DSP pitches, press one-sheets, and production specs.
Manage music release campaigns using RELEASE.md as the single source of truth.
Releases live inside an artist workspace under releases/. The full path from the sandbox root:
orgs/{org}/
└── artists/
└── {artist-slug}/
└── releases/
└── {release-slug}/
└── RELEASE.md
Use lowercase-kebab-case for release slugs (e.g. blue-slide-park, debut-ep).
Example:
orgs/recoup-records/artists/gatsby-grace/releases/adhd-ep/
└── RELEASE.md
When the user mentions a release, infer:
blue-slide-park)If unclear, ask:
"Which artist and release are you referring to?"
Once artist and release are identified:
1. Navigate to: orgs/{org}/artists/{artist-slug}/releases/{release-slug}/
2. Check if RELEASE.md exists
3. If YES → Read it and proceed
4. If NO → Ask: "No RELEASE.md found for [Release]. Should I create one?"
| User Intent | Action |
|---|---|
| Discussing a release | Read RELEASE.md, use as context |
| Adding information | Update the relevant section(s) |
| Asking for a deliverable | Pull data from RELEASE.md, generate output |
| Starting a new release | Create folder structure + RELEASE.md from template |
# 1. Create the folder structure (from sandbox root)
mkdir -p "orgs/{org}/artists/{artist-slug}/releases/{release-slug}"
# 2. Create RELEASE.md from template
# 3. Fill Section 1 (Project Snapshot) first
[INTERNAL], [SHAREABLE], [OPS] control distribution| Tag | Meaning |
|---|---|
[INTERNAL] | Scrub before sharing externally |
[SHAREABLE] | Safe for publicists, DSPs, management, agents |
[OPS] | Operations/production team reference |
| Section | Purpose | Sharing |
|---|---|---|
| 1. Project Snapshot | Core release info | SHAREABLE |
| 2. Release Identifiers & Metadata | UPCs, ISRCs, track data | OPS |
| 3. Narrative & Positioning | Pitch, story, comparables | SHAREABLE |
| 4. Artist Background | Bio, streaming history | SHAREABLE |
| 5. Audience & Market Data | Demographics, geo data | SHAREABLE |
| 6. DSP & Streaming Strategy | Pitches, playlist targets | SHAREABLE |
| 7. Marketing Strategy | Campaign goals, KPIs | INTERNAL |
| 8. Social & Digital Marketing | Organic, paid, influencer | INTERNAL |
| 9. PR & Media Relations | Press targets, materials | SHAREABLE |
| 10. Visual & Creative Assets | Artwork, videos, canvases | SHAREABLE |
| 11. Physical Production | Vinyl, CD, cassette specs | OPS/INTERNAL |
| 12. Merch | Items, strategy | INTERNAL |
| 13. Experiential & OOH | Events, billboards | INTERNAL |
| 14. Touring & Live | Dates, venues, routing | SHAREABLE |
| 15. Team Contacts | All stakeholders | INTERNAL |
| 16. Budget Overview | Allocated/spent/remaining | INTERNAL |
| 17. Performance Tracking | Weekly KPIs, learnings | INTERNAL |
| 18. Links & Resources Hub | All asset links | — |
See references/deliverables.md for output patterns:
When generating any deliverable:
The full release template is in references/release-template.md. Copy this file to start a new release.
See references/section-guide.md for detailed guidance on each section, including:
Before announcement, verify these sections are complete:
User: "Create a RELEASE.md for the new album 'Decisions'"
Process:
- Release = "Decisions", slug =
decisions- Create
releases/decisions/RELEASE.mdfrom template- Ask: "What's the release date?" (to fill Section 1)
User: "Update the 'Sunrise' RELEASE.md with these ISRCs"
Process:
- Release = "Sunrise", slug =
sunrise- Open
releases/sunrise/RELEASE.md- Update Section 2.2 with ISRC data
- If file not found → "No RELEASE.md for 'Sunrise'. Should I create one?"
User: "Generate a DSP pitch from the Midnights RELEASE.md"
Process:
- Read
releases/midnights/RELEASE.md- Pull data from Sections 1, 3, 4, 5, 6
- Format per
deliverables.mdspec- If missing fields → "Missing [fields]. Proceed with gaps noted?"
User: "What's missing from the 'For All The Dogs' release doc?"
Process:
- Read
releases/for-all-the-dogs/RELEASE.md- Run through Pre-Release Checklist
- Report incomplete sections