القائمة
Produces and updates a single-source-of-truth release plan markdown — covers metadata, assets, splits, distribution, and marketing milestones. Use when starting or updating a release.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Drive the running Ikenga desktop app from a Claude Code session — read its DOM, query its TanStack cache, navigate panes, capture screenshots, click and type. ALSO the multi-agent orchestration surface — spawn and control terminals running any LLM CLI, coordinate through scratchpads, todos, locks and leases, and read or write the task board. Use when the user is running the desktop app (or asks you to verify something inside it), or when you are orchestrating several agents or terminals to carry out multi-phase work.
Author a self-contained interactive HTML artifact (dashboard, view, comparison, mockup) that renders standalone in any browser AND lights up with live data when opened inside the Ikenga shell. Replaces .md for visual/interactive/data-bearing outputs. TRIGGER when: the user asks for a dashboard, view, summary-as-page, comparison, mockup, prototype, "make me an HTML…", or any output where interactivity or live data adds value over static text. Also trigger when CLAUDE.md / memory has a rule preferring artifacts over .md for visual outputs. DO NOT TRIGGER for: prose, technical writeups, decision docs, READMEs, long-form explanations, code reviews — those stay as .md.
Drafts a short changelog or newsletter entry from a list of shipped items. Use for weekly recaps, "what's new" posts, and product update emails.
Drafts short outreach emails (pitches, follow-ups, intros) for music-industry contacts using a strict house style. Use whenever an outbound email needs to be written.
Captures source-cited research notes from web searches and document reads. Use before drafting any content where facts matter.
Produces a per-track brief with metadata, credits, and pitch hooks. Use when adding a track to a release plan or preparing pitch sheets for DSPs / press.
| name | release-planner |
| description | Produces and updates a single-source-of-truth release plan markdown — covers metadata, assets, splits, distribution, and marketing milestones. Use when starting or updating a release. |
Maintains one markdown plan per release with five canonical sections so the team always knows what's missing.
# Release · {Artist} — {Title}
- Format: {single | EP | album}
- Release date: {YYYY-MM-DD}
- UPC: {…}
- Primary territory: {…}
## Assets
- [ ] Final masters (WAV, 44.1/24)
- [ ] Cover artwork (3000×3000 PNG/JPG)
- [ ] Press shots
- [ ] Lyric sheet
- [ ] Credits sheet
## Metadata
- [ ] ISRCs assigned per track
- [ ] Songwriter splits documented
- [ ] Producer / engineer credits
## Splits & Rights
- [ ] Recording splits signed
- [ ] Publishing splits documented
- [ ] PRO registrations queued
## Distribution
- [ ] DSP delivery scheduled
- [ ] Pre-save link live
- [ ] Sync clearances (if needed)
## Marketing
- [ ] Announcement date
- [ ] Press list
- [ ] Social calendar
- [ ] Newsletter slot
releases/{YYYY-MM-DD}-{slug}.md using the
template.