Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
recoupable avatar

Release Management

  • 1.6k installs
  • 1 repo stars
  • Updated February 17, 2026
  • recoupable/release-management

release-management maintains RELEASE.md documents and generates music release campaign deliverables.

About

The release-management skill organizes artist release workflows around RELEASE.md files stored under orgs/{org}/artists/{artist}/releases/{slug}/. Agents infer organization, artist, and release from context, check for existing RELEASE.md, create folder structures from templates, update sections without fabricating data, and generate deliverables like DSP pitches, press one-sheets, and production specs. Sharing tags INTERNAL, SHAREABLE, and OPS control distribution sensitivity across eighteen document sections from project snapshot through document history. Principles require confirming the release before edits, proactive section filling as facts arrive, and never inventing missing metadata. Use when users discuss albums, EPs, singles, release planning, marketing materials, or physical production for artist workspaces.

  • Uses RELEASE.md as single source of truth per release slug folder.
  • Creates, updates, and pulls DSP pitches and press deliverables.
  • Applies INTERNAL, SHAREABLE, and OPS sharing tags by section.
  • Never fabricates missing release metadata or tour facts.
  • Confirms artist and release identity before structural changes.

Release Management by the numbers

  • 1,572 all-time installs (skills.sh)
  • Ranked #377 of 1,879 Marketing & SEO skills by installs in the Skillselion catalog
  • Security screen: MEDIUM risk (skills.sh audit)
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
At a glance

release-management capabilities & compatibility

Capabilities
release.md lifecycle · campaign deliverables · sharing tag governance
Use cases
marketing · project management
From the docs

What release-management says it does

Manage music release campaigns using RELEASE.md as the single source of truth.
SKILL.md
npx skills add https://github.com/recoupable/release-management --skill release-management

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs1.6k
repo stars1
Security audit3 / 3 scanners passed
Last updatedFebruary 17, 2026
Repositoryrecoupable/release-management

How do I track and produce materials for an artist album or single release?

Manage music release campaigns using RELEASE.md as the single source of truth for metadata, DSP pitches, press, and tour coordination.

Who is it for?

Recoupable artist workspaces managing album, EP, or single campaigns.

Skip if: Non-music software release management or CI versioning.

When should I use this skill?

User mentions album release, DSP pitch, RELEASE.md, or artist campaign planning.

What you get

Updated RELEASE.md plus requested pitches or specs grounded only in documented facts.

  • RELEASE.md
  • DSP pitch documents
  • Press one-sheets

Files

SKILL.mdMarkdownGitHub ↗

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 IntentAction
Discussing a releaseRead RELEASE.md, use as context
Adding informationUpdate the relevant section(s)
Asking for a deliverablePull data from RELEASE.md, generate output
Starting a new releaseCreate folder structure + RELEASE.md from template

Creating a New Release

# 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

TagMeaning
[INTERNAL]Scrub before sharing externally
[SHAREABLE]Safe for publicists, DSPs, management, agents
[OPS]Operations/production team reference

Document Sections

SectionPurposeSharing
1. Project SnapshotCore release infoSHAREABLE
2. Release Identifiers & MetadataUPCs, ISRCs, track dataOPS
3. Narrative & PositioningPitch, story, comparablesSHAREABLE
4. Artist BackgroundBio, streaming historySHAREABLE
5. Audience & Market DataDemographics, geo dataSHAREABLE
6. DSP & Streaming StrategyPitches, playlist targetsSHAREABLE
7. Marketing StrategyCampaign goals, KPIsINTERNAL
8. Social & Digital MarketingOrganic, paid, influencerINTERNAL
9. PR & Media RelationsPress targets, materialsSHAREABLE
10. Visual & Creative AssetsArtwork, videos, canvasesSHAREABLE
11. Physical ProductionVinyl, CD, cassette specsOPS/INTERNAL
12. MerchItems, strategyINTERNAL
13. Experiential & OOHEvents, billboardsINTERNAL
14. Touring & LiveDates, venues, routingSHAREABLE
15. Team ContactsAll stakeholdersINTERNAL
16. Budget OverviewAllocated/spent/remainingINTERNAL
17. Performance TrackingWeekly KPIs, learningsINTERNAL
18. Links & Resources HubAll asset links

Generating Deliverables

See references/deliverables.md for output patterns:

  • DSP Pitch — Pull from Sections 1, 3, 4, 5, 6
  • Press One-Sheet — Pull from Sections 1, 3, 4, 9, 10
  • Physical Production Spec — Pull from Sections 2, 11
  • Marketing Brief — Pull from Sections 1, 3, 5, 6, 7, 8
  • Tour Marketing Brief — Pull from Sections 1, 3, 5, 14

When generating any deliverable: 1. Check RELEASE.md for required data 2. Identify missing fields 3. Request missing info from user OR generate with gaps noted 4. Format per deliverable spec

Template

The full release template is in references/release-template.md. Copy this file to start a new release.

Section Deep-Dive

See references/section-guide.md for detailed guidance on each section, including:

  • What each field means
  • Common data sources
  • Best practices for filling out
  • Red flags to watch for

Workflows

New Release Setup

1. Copy template → RELEASE.md 2. Fill Section 1 (Project Snapshot) 3. Fill Section 2.2 (Track Metadata) as available 4. Draft Section 3 (Narrative & Positioning) 5. Pull artist data for Sections 4-5 6. Build DSP pitch (Section 6) 7. Continue through remaining sections as timeline progresses

Pre-Release Checklist

Before announcement, verify these sections are complete:

  • [ ] Section 1: All dates confirmed
  • [ ] Section 2: UPC assigned, ISRCs for all tracks
  • [ ] Section 3: Pitch and narrative finalized
  • [ ] Section 6: DSP pitch submitted
  • [ ] Section 9: Press materials ready
  • [ ] Section 10: All visual assets delivered

Release Week Checklist

  • [ ] Section 6: Pre-save links live
  • [ ] Section 7: Phase 2 actions executing
  • [ ] Section 8: Paid ads launched
  • [ ] Section 9: Press embargo lifted
  • [ ] Section 17: Tracking dashboard ready

Post-Release

  • [ ] Section 17: Weekly KPIs logged
  • [ ] Section 17: Wins and learnings documented
  • [ ] Document History updated

Example Interactions

Creating a new release

User: "Create a RELEASE.md for the new album 'Decisions'"

>

Process:
1. Release = "Decisions", slug = decisions
2. Create releases/decisions/RELEASE.md from template
3. Ask: "What's the release date?" (to fill Section 1)

Adding metadata

User: "Update the 'Sunrise' RELEASE.md with these ISRCs"

>

Process:
1. Release = "Sunrise", slug = sunrise
2. Open releases/sunrise/RELEASE.md
3. Update Section 2.2 with ISRC data
4. If file not found → "No RELEASE.md for 'Sunrise'. Should I create one?"

Generating a deliverable

User: "Generate a DSP pitch from the Midnights RELEASE.md"

>

Process:
1. Read releases/midnights/RELEASE.md
2. Pull data from Sections 1, 3, 4, 5, 6
3. Format per deliverables.md spec
4. If missing fields → "Missing [fields]. Proceed with gaps noted?"

Checking release status

User: "What's missing from the 'For All The Dogs' release doc?"

>

Process:
1. Read releases/for-all-the-dogs/RELEASE.md
2. Run through Pre-Release Checklist
3. Report incomplete sections

Related skills

How it compares

Choose release-management for music RELEASE.md campaigns; choose software release-management skills when shipping versioned code artifacts to package registries.

FAQ

Where does release data live?

In RELEASE.md under orgs/{org}/artists/{artist-slug}/releases/{release-slug}/.

Can agents invent tour dates or metadata?

No. Leave sections blank when information is missing.

What deliverables can be generated?

DSP pitches, press one-sheets, production specs, and related release outputs from RELEASE.md.

Is Release Management safe to install?

skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.

Marketing & SEOcontentdistribution

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.