Release Management
Indie artists and small labels use it to keep one RELEASE.md per project and spin out DSP pitches, press one-sheets, and production specs without scattered notes.
Overview
Release-management is an agent skill most often used in Launch (also Validate and Grow) that manages music releases via RELEASE.md and generates distribution and press deliverables for indie artists.
Install
npx skills add https://github.com/recoupable/release-management --skill release-managementWhat is this skill?
- Uses RELEASE.md under orgs/{org}/artists/{artist-slug}/releases/{release-slug}/ as the single source of truth
- Step 1 infers organization, artist, release name, and kebab-case slug before reading or creating docs
- Generates DSP pitches, press one-sheets, and production specs from release data
- Covers release planning, metadata, marketing, press, physical production, and tour coordination
- Triggers on album, EP, single, or project mentions plus release-planning questions
- Single source of truth file: RELEASE.md per release slug
- Path pattern: orgs/{org}/artists/{artist-slug}/releases/{release-slug}/
- Step 1: infer organization, artist, release name, and release slug before editing
Adoption & trust: 1.3k installs on skills.sh; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You are juggling an album or single launch across metadata, DSP pitching, press, and production notes with no single document your agent can trust.
Who is it for?
Solo artists or indie labels already using the orgs/artists/releases workspace layout who want one RELEASE.md hub per project.
Skip if: Generic SaaS shipping, code releases, or teams with no artist workspace or music release context.
When should I use this skill?
User mentions an artist album, EP, single, or project, or asks about release planning, DSP pitches, metadata, marketing, press materials, physical production, or tour coordination.
What do I get? / Deliverables
You get a maintained RELEASE.md per release slug plus ready DSP pitches, press one-sheets, and production specs aligned to that file.
- RELEASE.md created or updated per release slug
- DSP pitch copy
- Press one-sheet and production spec outputs
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Release campaigns center on getting music onto DSPs and coordinated go-live, which maps to Launch and distribution as the canonical shelf even though planning starts earlier. DSP pitches, metadata, and distribution-facing deliverables are the core outputs named in the skill description.
Where it fits
Define EP scope, track list, and timeline in a new RELEASE.md before committing to production spend.
Centralize metadata, credits, and asset checklists in RELEASE.md while assets are prepared.
Generate DSP pitch copy and distribution-facing fields from the release document.
Align single or album storefront metadata and positioning with the same RELEASE.md source.
Export press one-sheets and marketing talking points for blogs, playlists, and tour promo.
How it compares
Use for music campaign documents and pitches, not DevOps semver or GitHub release automation skills.
Common Questions / FAQ
Who is release-management for?
Indie musicians, small labels, and solo operators who manage releases inside an artist workspace and want RELEASE.md to drive pitches and specs.
When should I use release-management?
At validate time to scope a single or EP, during build when filling metadata and assets, at launch for DSP pitches and distribution copy, and in grow for press one-sheets and marketing coordination.
Is release-management safe to install?
It expects filesystem access under your artist tree; review the Security Audits panel on this page before granting repo or sandbox write access.
SKILL.md
READMESKILL.md - Release Management
# Music Release Management Manage music release campaigns using RELEASE.md as the single source of truth. ## Folder Structure 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 ``` ## Step 1: Identify the Release When the user mentions a release, infer: 1. **Organization** — From the sandbox structure or conversation context 2. **Artist** — From the current workspace, conversation history, or ask 3. **Release Name** — Album title, EP name, single title 4. **Release slug** — Derive from the name (e.g. "Blue Slide Park" → `blue-slide-park`) **If unclear, ask:** > "Which artist and release are you referring to?" ## Step 2: Check if RELEASE.md Exists 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?" ``` ## Step 3: Create, Update, or Pull | 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 | ### Creating a New Release ```bash # 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 ``` ### Updating an Existing Release 1. Read the current RELEASE.md 2. Identify which section(s) need updates 3. Update only those sections 4. Note changes in Document History (Section 18) ## Core Principles 1. **Never fabricate data** — Leave sections blank if information is missing 2. **Be proactive** — Fill sections as information becomes available 3. **Respect sharing tags** — `[INTERNAL]`, `[SHAREABLE]`, `[OPS]` control distribution 4. **One document per release** — All release info lives in RELEASE.md 5. **Always confirm the release** — Before making changes, confirm which release. ## Sharing Tags | Tag | Meaning | |-----|---------| | `[INTERNAL]` | Scrub before sharing externally | | `[SHAREABLE]` | Safe for publicists, DSPs, management, agents | | `[OPS]` | Operations/production team reference | ## Document Sections | 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