release-management

This skill manages music release campaigns using a single RELEASE.md document per release as the source of truth. Release documents live in a structured artist workspace under `orgs/{org}/artists/{artist-slug}/releases/{release-slug}/`, and the skill triggers whenever a user mentions an artist's album, EP, single, or project, or asks about release planning, DSP pitches, metadata, marketing, press, physical production, or touring. It solves the problem of scattered, inconsistent release information by centralizing everything for a release into one well-structured living document.

The documented workflow is: identify the release (inferring organization, artist, name, and a kebab-case slug, asking when unclear), check whether RELEASE.md exists and create it from a template if not, then create, update, or pull data from it. The document is organized into 18 sections spanning project snapshot, identifiers and metadata (UPCs, ISRCs), narrative and positioning, artist background, audience data, DSP and streaming strategy, marketing, PR, visual assets, physical production, merch, experiential, touring, team contacts, budget, and performance tracking. Sharing tags ([INTERNAL], [SHAREABLE], [OPS]) control what may be distributed externally. From this single source the skill generates deliverables — DSP pitches, press one-sheets, physical production specs, and marketing and tour briefs — each pulling from a defined set of sections. Core principles stress never fabricating data, leaving missing fields blank, updating only relevant sections, and always confirming which release is meant. Reference files provide the template, section guide, and deliverable patterns, plus workflow checklists for new-release setup, pre-release, release week, and post-release.

It targets record labels, artist managers, and music marketing teams who want a consistent, document-driven way to plan and coordinate releases and produce shareable materials.