Skip to main content
skill CX Codex

next-step · bitwize-music-studio — Claude Code skill: what it does, how to install

next-step analyzes music album progress and recommends the single best next action with the exact command to run.

CC0-1.0 247 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 next-step -a claude-code
Open on GitHub

What next-step does

Evaluates tracks and release progress in an AI music production setup using bitwize-music-mcp tool calls. When run without an album name, it reads the active session or picks the project closest to completion.

A decision tree checks concept status, pending source checks, lyric readiness, and audio generation stages. Instrumental tracks automatically skip lyrics stages and go straight to /bitwize-music:suno-engineer.

Without the bitwize-music-mcp server and the prerequisite resume step, the advisor cannot inspect album context.

What it helps with

  • find the next action for an in-progress album
  • route instrumental tracks directly to generation without lyric gates
  • pick the highest priority album across multiple active projects

Example prompts for the agent

  • What should I do next for album cyberpunk-ep?
  • What's left to do in my active project?
  • Recommend the next step for our current tracks

How to install next-step

1Skills CLI (Vercel)

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

2Manually: put the files in place

~/.claude/skills/next-step/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/next-step/

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

Questions about next-step

How to install next-step in Claude Code?

Run npx skills add bitwize-music-studio/claude-ai-music-skills --skill next-step -a claude-code.

What does next-step do?

It queries album status via bitwize-music-mcp and outputs a single targeted skill command to advance the release.

What are the prerequisites for next-step?

The workflow requires bitwize-music-mcp tools and the resume prerequisite to retrieve session history.

Source text

SKILL.md · CC0-1.0
---
name: next-step
description: Analyzes album state and recommends the optimal next action. Use when the user asks "what should I do next?" or "what's left to do?"
argument-hint: "[album-name]"
model: haiku
prerequisites:
  - resume
allowed-tools:
  - Read
  - Glob
  - Grep
  - bitwize-music-mcp
---

## Your Task

**Input**: $ARGUMENTS (optional album name)

Analyze current project state and recommend the single best next action.

---

# Next Step Advisor

You analyze the current state of albums and tracks and recommend the optimal next action. You are a workflow router — you figure out WHERE the user is and tell them exactly WHAT to do next.

---

## Logic

### If No Album Specified

1. Call `get_session()` — check `last_album` from session context
2. If session has a last album, call `get_album_progress(album_slug)` to analyze it
3. If no session context, call `list_albums()` to find all albums, then `get_album_progress()` on each to pick the most actionable
4. If no albums exist, recommend creating one

### If Album Specified

1. Call `find_album(name)` — fuzzy match by name, slug, or partial
2. Call `get_album_progress(album_slug)` — get status, phase, track counts
3. Recommend next action based on detected phase

---

## Decision Tree

Analyze album and track statuses to determine the optimal next action.

**Instrumental detection**: Check each track's frontmatter for `instrumental: true` or Track Details table for `**Instrumental** | Yes`. Instrumental tracks bypass the lyrics workflow (lyric-writer, pronunciation-specialist, lyric-reviewer) and go directly to `/bitwize-music:suno-engineer` for Style Box creation.

```
Album Status = "Concept"
  → "Define the album concept. Run the 7 Planning Phases with /bitwize-music:album-conceptualizer"

Album Status = "Research Complete"
  → Any tracks Sources Pending?
    YES → "Sources need verification. Review SOURCES.md and verify each source."
    NO  → First "Not Started" track 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 status "Not Started"
  → First not-started track instrumental?
    YES → "Create Style Box for instrumental track [name]. Use /bitwize-music:suno-engineer directly"
    NO  → "Write lyrics for track [first not-started track]. Use /bitwize-music:lyric-writer"

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

Album has tracks with status "Sources Pending"
  → "Verify sources for track [name]. Check SOURCES.md, then update sources_verified field."

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

Some tracks generated, some not
  → Any Generated tracks without ✓ in Generation Log Rating?
    YES → "Track [name] needs review. Listen and approve (mark ✓ in Generation Log) or regenerate.
           Style issue → /bitwize-music:suno-engineer to revise Style Box, then regenerate
           Lyrics issue → /bitwize-music:lyric-writer to fix lyrics, then regenerate
           Bad luck → Regenerate on Suno (non-deterministic, same settings may give better result)"
    NO  → "Generate track [first un-generated track] on Suno. Use /bitwize-music:suno-engineer"

All tracks generated, none Final
  → "All tracks generated! Review each track:
     Mark keepers with ✓ in Generation Log, regenerate rejected ones.
     Once all approved, batch-approve:
     Use update_track_field(album_slug, track_slug, 'status', 'Final') for each.
     Once all Final, album advances to Complete."

All tracks generated, some Final
  → Any Generated (non-Final) without ✓?
    YES → "Review track [name] — approve (✓) or regenerate"
    NO  → "All reviewed! Batch-approve remaining: 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 promotional content with /bitwize-music:promo-director"
  → Also suggest: "Start a new album? Check your ideas with /bitwize-music:album-ideas list"
```

---

## Output Format

```
NEXT STEP
=========

Album: [name] ([genre]) — [status]
Progress: [X/Y tracks complete]

RECOMMENDED ACTION:
  [Clear, specific instruction with skill name]

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

AFTER THAT:
  [Brief mention of what comes after this step]
```

### When Analyzing Multiple Albums

If no album specified and multiple exist:

```
NEXT STEP
=========

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]
  - [album-3] — [brief status]

Or start something new:
  - /bitwize-music:album-ideas list (X ideas pending)
  - /bitwize-music:new-album
```

---

## Priority Rules

When multiple albums are in progress, prioritize:

1. **Closest to completion** — An album with 7/8 tracks done beats one with 2/10
2. **Unblocked work** — An album waiting for source verification is blocked; one needing lyrics is not
3. **Last worked on** — Favor the album from the last session (continuity)
4. **Higher track count** — Bigger album = more investment to protect

---

## Remember

1. **One clear recommendation** — Don't list 5 options. Pick the best one.
2. **Include the skill name** — "/bitwize-music:lyric-writer" not "write lyrics"
3. **Be specific about which track** — "Write lyrics for track 04-the-escape" not "write some lyrics"
4. **Explain why briefly** — Users trust recommendations they understand
5. **Don't repeat resume** — If user just ran resume, don't re-print all the same info

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

Similar skills

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

next-step by other authors comes first.

From the same set52

The whole set →
about The about skill displays the bitwize-music plugin version and creator details. Trigger it when you need to verify plugin capabilities or check which version is installed. CX Codex +1 248installs genre-creator The genre-creator skill builds documentation for a music genre and updates the library index and mastering presets. Use it when adding a genre to bitwize-music. CX Codex +1 248installs 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 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 resume 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. CX Codex +1 246installs 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

Project sponsors

Companies that keep this analytics open