mcpField
N
next-step

next-step

github.com/bitwize-music-studio创意与媒体603217 次安装2 周前更新
代码仓库

关于 next-step

面向 Bitwize Music 工作流的建议 skill,可检查专辑与曲目进度并推荐一个下一步操作。它结合会话信息、专辑状态和器乐曲规则,将任务指向相应 skill。

主要功能

  1. 01根据名称或会话查找专辑
  2. 02检查专辑与曲目进度
  3. 03按工作流阶段选择下一步
  4. 04让器乐曲跳过歌词环节
  5. 05在多个进行中专辑间确定优先级

适用场景

  1. 01为专辑选择下一项任务
  2. 02根据会话信息继续工作
  3. 03将器乐曲转至风格创作步骤

安装

复制下面的命令,在终端中运行。

$npx skills add https://github.com/bitwize-music-studio/claude-ai-music-skills --skill next-step

安装后在 Claude Code 中输入/next-step确认已加载。

详细介绍

你的任务

输入:$ARGUMENTS(可选的专辑名称)

分析当前项目状态,并推荐唯一的最佳下一步操作。


下一步顾问

你会分析专辑和曲目的当前状态,并推荐最佳下一步操作。你是一个工作流路由器——确定用户当前所处的位置,并明确告知他们接下来该做什么。


逻辑

未指定专辑时
  1. 调用 get_session()——从会话上下文中检查 last_album
  2. 如果会话中有上次处理的专辑,调用 get_album_progress(album_slug) 进行分析
  3. 如果没有会话上下文,调用 list_albums() 查找所有专辑,然后对每张专辑调用 get_album_progress(),选出最适合采取行动的一张
  4. 如果不存在专辑,建议创建一张
指定专辑时
  1. 调用 find_album(name)——按名称、slug 或部分名称进行模糊匹配
  2. 调用 get_album_progress(album_slug)——获取状态、阶段和曲目数量
  3. 根据检测到的阶段推荐下一步操作

决策树

分析专辑和曲目的状态,以确定最佳下一步操作。

器乐曲检测:检查每首曲目的 frontmatter 是否包含 instrumental: true,或曲目详情表中是否有 **Instrumental** | Yes。器乐曲会跳过歌词工作流(lyric-writer、pronunciation-specialist、lyric-reviewer),直接进入 /bitwize-music:suno-engineer 创建 Style Box。

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"

输出格式

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]
分析多张专辑时

如果未指定专辑且存在多张专辑:

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

优先级规则

当多张专辑正在处理中时,按以下顺序确定优先级:

  1. 最接近完成——已完成 7/8 首曲目的专辑优先于已完成 2/10 首的专辑
  2. 未受阻的工作——等待来源核实的专辑处于受阻状态;需要歌词的专辑则没有受阻
  3. 最近处理过的专辑——优先选择上次会话中处理的专辑(保持连贯性)
  4. 曲目数量更多——专辑越大,越值得保护已投入的工作

请记住

  1. 只给出一个明确建议——不要列出 5 个选项。选出最佳的一项。
  2. 注明技能名称——使用“/bitwize-music:lyric-writer”,而不是“写歌词”
  3. 明确指出曲目——“为曲目 04-the-escape 写歌词”,而不是“写一些歌词”
  4. 简要说明原因——用户理解建议的理由后会更信任它
  5. 不要重复 resume 的内容——如果用户刚运行过 resume,不要再次输出完全相同的信息

评论

支持 Markdown