Update to Artispreneur

{
  "description": "Build a dated release rollout counted back from the release day: asset lock, metadata and splits, distributor upload, editorial pitch, pre-save, content, outreach, registrations, release day, and the first 30 days, with warnings when dates are too tight. Use when the user gives a release date or says 'plan my release', 'rollout plan', 'release timeline', or 'drop strategy'.",
  "included_files": [],
  "name": "release-music-with-dsp",
  "skill_md_contents": "---\nname: release-music-with-dsp\ndescription: \"Build a dated release rollout counted back from the release day: asset lock, metadata and splits, distributor upload, editorial pitch, pre-save, content, outreach, registrations, release day, and the first 30 days, with warnings when dates are too tight. Use when the user gives a release date or says 'plan my release', 'rollout plan', 'release timeline', or 'drop strategy'.\"\nmetadata:\n  author: Artispreneur\n  version: \"2.0.0\"\n  desk: Release\n  group: \"Release & DSP\"\n  display_name: \"Release Engine\"\n  website: https://www.artispreneur.com\n---\n\n# Release Engine\n\n> A release plan that works backward from drop day.\n> *Release desk · Release & DSP · about 25 minutes*\n\n## When to use\n\n- A release date exists or needs to be chosen.\n- The artist wants a checklist instead of guessing.\n- A date feels too close and needs a reality check.\n\n## Ask first\n\nRead the artist profile first (`artist-profile.md`, or the profile pasted in chat) and only ask for what is missing. Ask in one short batch.\n\n- Release date (or target window) and today's date.\n- Release type and number of tracks.\n- Which assets exist: master, artwork, metadata, video, lyrics.\n- Budget and hours per week available.\n- Distributor and whether editorial pitching is planned.\n\n## Workflow\n\n1. Count back from release day using the offsets below, adjusting for assets already finished.\n2. Flag timeline risks: distributor upload later than about two weeks before release, or an editorial pitch inside seven days, is at risk. Four weeks for upload and three weeks for pitching is the comfortable target.\n3. Attach each milestone to the skill that does it.\n4. Add a weekly rhythm for the final three weeks (teasers, outreach, community).\n5. Write the day-of checklist and the first-30-days plan (follow-ups, playlist pitching, analytics review, thank-yous).\n6. State clearly that nothing is scheduled or submitted by this plan.\n\n## Deliverables\n\n- Dated milestone list.\n- Risk flags.\n- Release-day and first-30-days checklists.\n\nSave each deliverable as a Markdown file if file tools are available; otherwise present it in the conversation.\n\n## Output template\n\nOffsets from release day (T):\n- T minus 8 weeks: asset lock (final master, artwork, video plan)\n- T minus 6 weeks: metadata, credits, splits signed\n- T minus 4 weeks: deliver to distributor (no later than T minus 2 weeks)\n- T minus 3 weeks: submit editorial pitch in the DSP's artist tools (no later than T minus 7 days); pre-save link live; teasers begin\n- T minus 3 to 1 weeks: outreach to press, curators, and community\n- T minus 1 week: confirm registrations are in place (PRO, MLC, SoundExchange)\n- T: release day\n- T plus 1 to 30 days: follow-ups, playlist pitching, analytics review, content from the release\n\n## Quality checks (run before handing over)\n\n- [ ] Every milestone has a date.\n- [ ] Risk flags are shown wherever the date is inside the minimum window.\n- [ ] The plan never claims anything is scheduled.\n- [ ] Milestones match the assets that actually exist.\n\n## Guardrails\n\n- Do not promise editorial placement or playlist adds.\n- Do not schedule spend the artist did not approve.\n- Never invent facts, numbers, credits, quotes, placements, or contacts. If the artist has not supplied something, ask or mark it `[CONFIRM]`.\n- Label every estimate as an ESTIMATE and show the formula or assumption behind it.\n- Never collect, solicit, or process Restricted Data: payment card data (PCI DSS), protected health information (PHI), government identifiers (Social Security numbers, ITINs, EIN digits, passport or driver's license numbers), or access credentials and authentication secrets (passwords, API keys, MFA/OTP codes, bank logins). The artist enters sensitive information directly on official sites.\n- Gather only the minimum task-specific input required; never request full conversation history, raw chat transcripts, or precise user location data (street addresses or GPS coordinates).\n- Do not display subscription plans, promote paid upgrades, sell digital goods/credits, or embed checkout flows.\n- Draft first. Never claim anything was filed, registered, sent, posted, uploaded, or paid. The artist takes every outside action.\n\n## Hand-offs\n\n- `distribution-readiness`: verify the delivery\n- `create-content-calendar`: plan the teasers\n- `pr-campaign`: press outreach\n- `playlist-outreach`: curator pitches\n- `register-tracks-with-pro`: registrations\n\n## Start with\n\n> My single comes out on this date. Build the plan counting back from it.\n\n---\n*Artispreneur · Art Means Business · https://www.artispreneur.com*\n"
}