Skip to main content
skill CX Codex

resume · bitwize-music-studio — Claude Code skill: find an album and resume work

resume finds an album by name and displays its status with a concrete next step. Use when returning to an unfinished project or checking where an album stands in its workflow.

CC0-1.0 246 installs ★ 686 updated 2026-10-22

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add bitwize-music-studio/claude-ai-music-skills --skill resume -a claude-code
Open on GitHub

What resume does

Resume locates an album by fuzzy-matching its name (case-insensitive), then reports progress: track counts by status, detected workflow phase, and one specific recommendation for what to do next.

The skill integrates with the bitwize-music-mcp server and uses Read, Glob, and Bash. If cache is stale, it rebuilds state automatically. Handles both vocal albums (with lyrics and Suno generation) and documentary projects (with a source-verification stage). Instrumental tracks bypass the lyric-writing phase and route directly to Suno.

Available in Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, and OpenCode. Requires bitwize-music-mcp in your MCP allowlist.

What it helps with

  • locate an album by name across multiple projects
  • check where an album stands in its workflow phase
  • get a single, concrete recommendation for the next action
  • distinguish instrumental tracks from vocal tracks in the workflow
  • restore session context after stepping away from a project

Example prompts for the agent

  • Run /bitwize-music:resume my-album to see progress and next steps
  • Call /bitwize-music:resume "demo album" if the name contains spaces
  • Tell the agent: 'Resume work on my-acoustic-songs and show me what's next'

How to install resume

1Skills CLI (Vercel)

npx skills add bitwize-music-studio/claude-ai-music-skills --skill resume -a claude-code

2Manually: put the files in place

~/.claude/skills/resume/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/resume/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about resume

How do I install resume in Claude Code?

Run npx skills add bitwize-music-studio/claude-ai-music-skills --skill resume -a claude-code, then check ~/.claude/skills/resume/SKILL.md. The command becomes available as /bitwize-music:resume.

What does resume do?

Finds an album by name, counts tracks by status, detects the current workflow phase, and recommends one specific action. For example, if all tracks are ready for generation, it suggests running the pre-generation check; if some tracks lack lyrics, it recommends writing them.

Does resume work with documentary albums?

Yes. Documentary albums include a source-verification stage that vocal albums skip. Resume detects the album type and suggests the right skill for the next step.

Source text

SKILL.md · CC0-1.0
---
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 with same settings (it's non-deterministic)"
    NO  → "Generate [first un-generated track] on Suno. Use /bitwize-music:suno-engineer"

All tracks generated, none Final
  → "All tracks generated! Listen to each track and approve:
     - Mark keepers with ✓ in Generation Log Rating column
     - Reject and regenerate any that don't meet quality standards
     - Once all have ✓, batch-approve:
       Use update_track_field(album_slug, track_slug, 'status', 'Final') for each approved track.
       Once all Final, album advances to Complete automatically."

All tracks generated, some Final
  → Any Generated (non-Final) tracks without ✓?
    YES → "Review track [name] — listen and approve (✓) or regenerate"
    NO  → "All tracks approved! Batch-approve: update_track_field(album_slug, track_slug, 'status', 'Final') for each.
           Then import audio with /bitwize-music:import-audio, then master with /bitwize-music:mastering-engineer"

All tracks Final
  → "All tracks approved! Import audio with /bitwize-music:import-audio, then master with /bitwize-music:mastering-engineer"

Album Status = "Complete"
  → "Album is complete! Release with /bitwize-music:release-director"

Album Status = "Released"
  → "This album is released! Consider /bitwize-music:promo-director for promotional content"
  → Also suggest: "Start a new album? Check /bitwize-music:album-ideas list"
```

**Format the recommendation as:**
```
RECOMMENDED NEXT ACTION:
  [Clear, specific instruction with skill name and track name]

WHY:
  [One sentence explaining why this is the right next step]
```

### When No Album Specified (No Arguments)

If invoked without an album name:
1. Call `get_session()` — check `last_album` from session context, resume that album
2. If no session context, call `list_albums()` to find all in-progress albums
3. Prioritize: closest to completion > unblocked work > last worked on
4. If no albums exist, suggest `/bitwize-music:new-album`

Present a multi-album summary if multiple are in progress:
```
You have X albums. Here's the most actionable:

PRIORITY 1: [album-name] ([genre])
  Status: [status] | Progress: [X/Y tracks]
  → [Recommended action]

Also in progress:
  - [album-2] — [brief status]
```

---

## Examples

### Example 1: Album in Writing Phase

```
/bitwize-music:resume my-album

📁 Album: My Album
   Location: ~/bitwize-music/artists/bitwize/albums/rock/my-album/
   Status: In Progress

📊 Progress:
   - Tracks: 3 completed / 8 total
   - Not Started: 3
   - In Progress: 2
   - Final: 3

📍 Current Phase: Writing Lyrics

✅ What's Done:
   - Tracks 1-3 have final lyrics
   - Album concept and tracklist defined

⏭️ Next Steps:
   1. Complete lyrics for Track 4 (in progress)
   2. Complete lyrics for Track 5 (in progress)
   3. Write lyrics for Tracks 6-8

Ready to continue? Tell me which track you'd like to work on.
```

### Example 2: Album Ready for Generation

```
/bitwize-music:resume demo-album

📁 Album: Demo Album
   Location: ~/bitwize-music/artists/bitwize/albums/electronic/demo-album/
   Status: In Progress

📊 Progress:
   - Tracks: 8 / 8 total (all lyrics complete)
   - Final: 8

📍 Current Phase: Ready to Generate

✅ What's Done:
   - All 8 tracks have complete lyrics
   - All lyrics phonetically reviewed
   - Suno Style and Lyrics boxes filled

⏭️ Next Steps:
   1. Run Ready to Generate checkpoint (I'll verify everything)
   2. Start generating on Suno
   3. Log generation attempts

Shall I run the Ready to Generate checkpoint now?
```

### Example 3: Album Not Found

```
/bitwize-music:resume my-album

❌ Album 'my-album' not found.

Available albums:
- demo-album (electronic) - In Progress
- example-tracks (hip-hop) - Complete

Did you mean one of these? Or use /bitwize-music:new-album to create a new album.
```

---

## Implementation Notes

- **Use MCP tools** - `find_album`, `get_album_progress`, `list_tracks`, `update_session` instead of reading state.json directly
- **Case-insensitive matching** - "Sample-Album" should match "sample-album"
- **Handle missing albums gracefully** - List what exists, don't error
- **Be specific about next steps** - Don't just say "continue working", say exactly what to do
- **Include full paths** - User needs to know where files are located
- **Use emojis sparingly** - Only for section headers in the report

---

## Model

Use **Sonnet 4.5** - This is a coordination/reporting task, not creative work.

© bitwize-music-studio · CC0-1.0 · bitwize-music-studio/claude-ai-music-skills

Similar skills

All skills for Agent setup: memory, context, orchestration →

resume by other authors comes first.

resume saksham10arora-dotcom resume is a Claude Code skill that reviews a CV against target roles and suggests edits. It activates when a user asks about a resume or wants to update one. CX Codex +1 ★ 101repo stars resume wrg32786 Restores context for unfinished work. Run /resume to compare the saved capsule with live memory and take the next step. CX Codex +1 ★ 26repo stars resume-handoff parcadei resume-handoff reads a handoff document, checks it against the actual repo state, and suggests a way forward. Useful when a session got cut off and the context needs to come back fast. CX Codex +1 486installs linear-tickets stablyai linear-tickets — a skill for Claude Code that runs Linear ticket workflows through the Orca CLI. It searches issues, transitions workflow states, and attaches pull request links upon completion. CX Codex +1 4,900installs Monday.com Automation Claude Office Skills Monday.com Automation is a Claude Code skill for managing Monday.com boards and automating workflows. It handles requests involving board items, configurations, and automation recipes. CX Codex +1 4,700installs w-plan blockmatic-icebox The w-plan Claude Code skill turns a project change into an ordered work plan. It inspects relevant context and task dependencies without modifying implementation. CX Codex +1 647installs gsd-ns-project open-gsd gsd-ns-project is a Claude Code skill that routes project lifecycle requests to the appropriate development phase handlers, including milestone operations. CX Codex +1 573installs integration-orchestrator rampstackco integration-orchestrator — a skill that builds a delivery plan for creative-direction projects: which phases run when, where decisions lock, who verifies what, and how to implement it in Jira, Linear, or Figma with agents. CX Codex +1 276installs

From the same set52

The whole set →
validate-album validate-album is a Claude Code skill that checks album directories, audio file paths, and track metadata before release. CX Codex +1 248installs researchers-financial researchers-financial is a Claude Code skill that researches financial records and market data for music projects about companies, financial crime, or market events. It gathers sources and marks claims for human review. CX Codex +1 248installs next-step next-step analyzes music album progress and recommends the single best next action with the exact command to run. CX Codex +1 247installs configure configure is a Claude Code skill that interactively creates, edits, and checks the ~/.bitwize-music/config.yaml configuration file. CX Codex +1 247installs cloud-uploader cloud-uploader is a skill for uploading album promo videos and samplers to Cloudflare R2 or AWS S3 after the videos are created. CX Codex +1 247installs researchers-primary-source The researchers-primary-source skill gathers statements from tweets, blogs, forums and chat logs. Use it when you need direct quotes or first-hand accounts instead of paraphrased reporting. CX Codex +1 246installs promote-idea promote-idea turns a pending album concept in IDEAS.md into a project with one command. Use it when an idea is ready to move into album planning. CX Codex +1 188installs health-check health-check — a skill that runs plugin diagnostics: checks virtual environment packages, verifies skill registration, and detects album slug collisions. Use it to confirm your setup is correct or troubleshoot missing components. CX Codex +1 187installs

Project sponsors

Companies that keep this analytics open