Skip to content

/resume

Finds an album by name and shows detailed status with next steps. Use when the user mentions an album name or wants to continue previous work.

shell
$ npx -y skills add bitwize-music-studio/claude-ai-music-skills --skill resume --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
  • You can call itInvoke it directly when you want it.
  • Slash command/resume
How auto-invocation works

Context preview

The summary Claude sees to decide when to auto-load this skill.

Finds an album by name and shows detailed status with next steps. Use when the user mentions an album name or wants to continue previous work.

SKILL.md

resume.SKILL.md
name: resume
description: Finds an album by name and shows detailed status with next steps. Use when the user mentions an album name or wants to continue previous work.
argument-hint: <album-name>
model: sonnet
effort: low
allowed-tools:
  - Read
  - Glob
  - Bash
  - bitwize-music-mcp

Resume Album Work

**Purpose**: Find an album and resume work where you left off.

**Usage**:

/bitwize-music:resume <album-name>
/bitwize-music:resume my-album
/bitwize-music:resume "demo album"

**When to use**: When user wants to continue working on an existing album.

---

Instructions

When this skill is invoked with an album name:

Step 1: Find the Album via MCP

1. Call `find_album(name)` — fuzzy match by name, slug, or partial (case-insensitive) 2. If not found: MCP returns available albums — suggest closest match or `/bitwize-music:new-album` 3. If multiple matches: list all with paths, ask user which one 4. If MCP returns stale/missing cache error: call `rebuild_state()` then retry

Step 2: Get Album Progress

1. Call `get_album_progress(album_slug)` — returns track counts by status, completion percentage, and detected workflow phase 2. Call `list_tracks(album_slug)` — returns per-track details (status, has_suno_link, sources_verified)

Step 3: Update Session Context

Call `update_session(album=album_slug, phase=detected_phase)` to set the active album and phase.

Step 4: Determine Current Phase

Based on album and track statuses, identify the workflow phase:

| Album Status | Track Statuses | Current Phase | |--------------|----------------|---------------| | Concept | Most "Not Started" | Planning - Need to fill in album README and create tracks | | Research Complete | Some "Sources Pending" | Verification - Need human verification of sources (documentary albums) | | Sources Verified | All sources verified | Ready to Write - Sources cleared, begin lyrics (documentary albums) | | In Progress | Mixed, some "Not Started" | Writing - Need to complete lyrics (or route instrumental tracks to suno-engineer) | | In Progress | Some "Sources Pending" | Verification - Need human verification of sources | | In Progress | All have lyrics | Ready to Generate - Run Ready to Generate checkpoint | | In Progress | Some "Generated" | Generating - Continue generating on Suno. Check Generation Logs for rejected tracks needing regeneration | | In Progress | All "Generated", none "Final" | Review & Approve - Listen to generated tracks, mark keepers with ✓, regenerate rejected ones | | Complete | All "Final" | Mastering - Ready to master audio | | Released | All "Final" | Released - Album is live |

**Note**: Non-documentary albums skip `Research Complete` and `Sources Verified` — they go directly from `Concept` → `In Progress`.

Step 5: Report to User

Present a clear status report:

📁 Album: [Album Title]
   Location: {content_root}/artists/{artist}/albums/{genre}/{album}/
   Status: [Album Status]

📊 Progress:
   - Tracks: [X completed / Y total] ([N vocal, M instrumental])
   - Not Started: X
   - In Progress: Y
   - Generated: Z
   - Final: N

📍 Current Phase: [Phase Name]

✅ What's Done:
   - [List completed items]

⏭️ Next Steps:
   1. [Specific action 1]
   2. [Specific action 2]
   3. [Specific action 3]

Ready to continue? Tell me what you'd like to work on.

Step 6: Recommend the Single Best Next Action

Pick ONE clear recommendation from the decision tree below. Don't list 5 options — pick the best one, include the skill name, and be specific about which track.

**Decision Tree** (evaluate top-to-bottom, first match wins):

**Instrumental detection**: Check each track's frontmatter for `instrumental: true` or Track Details table for `**Instrumental** | Yes`. Instrumental tracks skip the lyrics workflow entirely and go straight to `/bitwize-music:suno-engineer`.

Album Status = "Concept"
  → "Define the album concept. Run /bitwize-music:album-conceptualizer"

Album Status = "Research Complete"
  → Any tracks Sources Pending?
    YES → "Sources need verification. Run /bitwize-music:verify-sources [album]"
    NO  → Any "Not Started" tracks instrumental?
      YES → "Create Style Box for instrumental track [name]. Use /bitwize-music:suno-engineer"
      NO  → "Ready to write! Pick a track and use /bitwize-music:lyric-writer"

Album has tracks with "Not Started"
  → Is the first not-started track instrumental?
    YES → "Create Style Box for [track]. Use /bitwize-music:suno-engineer directly (instrumental track)"
    NO  → "Write lyrics for [first not-started track]. Use /bitwize-music:lyric-writer"

Album has tracks with "In Progress" (lyrics partially written)
  → "Finish lyrics for [first in-progress track]. Use /bitwize-music:lyric-writer"

Album has tracks with "Sources Pending"
  → "Verify sources for [track]. Run /bitwize-music:verify-sources [album]"

All tracks have lyrics (or Style Box for instrumentals), none generated
  → Mixed album (vocal + instrumental)?
    YES → "All tracks ready! Run /bitwize-music:pronunciation-specialist on vocal tracks, then /bitwize-music:lyric-reviewer, then /bitwize-music:pre-generation-check to validate all gates (instrumental tracks auto-skip lyrics gates)."
    NO  → "All lyrics complete! Style prompts should be ready. Run /bitwize-music:pronunciation-specialist to check for pronunciation risks, then /bitwize-music:lyric-reviewer for final QC, then /bitwize-music:pre-generation-check to validate all gates before generating on Suno."

Some tracks generated, some not
  → Any Generated tracks without ✓ in Generation Log Rating?
    YES → "Track [name] was generated but not approved. Listen and decide:
           - Happy? Mark ✓ in Generation Log and set Status: Final
           - Not happy? Log the reason, then:
             Style issue → /bitwize-music:suno-engineer to revise Style Box
             Lyrics issue → /bitwize-music:lyric-writer to fix, then regenerate
             Bad luck → Regenerate on Suno wit
Read more
Read it on GitHub ↗

Showing the first part of this file.

Ships withbitwize-music

I love music but never learned an instrument. AI became the creative outlet that was always out of reach. This project started as a way to go deep on Claude Code plugin architecture, agentic workflows, multi-model orchestration, and MCP tooling.

Get the whole plugin, auto-invoked
Stats
399
Stars
0
Views
93
Forks
Active
Maintenance
Python
Language
CC0-1.0
License
3d ago
Last commit
6mo ago
Created

Repo: bitwize-music-studio/claude-ai-music-skills