next-step
关于
The next-step skill analyzes album project states and recommends the optimal single next action when users ask "what should I do next?" It determines workflow position by checking session context or scanning all albums, then provides specific guidance. This skill acts as a workflow router, using tools like Read, Glob, and bitwize-music-mcp to assess progress and direct next steps.
快速安装
Claude Code
推荐npx skills add bitwize-music-studio/claude-ai-music-skills -a claude-code/plugin add https://github.com/bitwize-music-studio/claude-ai-music-skillsgit clone https://github.com/bitwize-music-studio/claude-ai-music-skills.git ~/.claude/skills/next-step在 Claude Code 中复制并粘贴此命令以安装该技能
技能文档
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
- Call
get_session()— checklast_albumfrom session context - If session has a last album, call
get_album_progress(album_slug)to analyze it - If no session context, call
list_albums()to find all albums, thenget_album_progress()on each to pick the most actionable - If no albums exist, recommend creating one
If Album Specified
- Call
find_album(name)— fuzzy match by name, slug, or partial - Call
get_album_progress(album_slug)— get status, phase, track counts - 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:
- Closest to completion — An album with 7/8 tracks done beats one with 2/10
- Unblocked work — An album waiting for source verification is blocked; one needing lyrics is not
- Last worked on — Favor the album from the last session (continuity)
- Higher track count — Bigger album = more investment to protect
Remember
- One clear recommendation — Don't list 5 options. Pick the best one.
- Include the skill name — "/bitwize-music:lyric-writer" not "write lyrics"
- Be specific about which track — "Write lyrics for track 04-the-escape" not "write some lyrics"
- Explain why briefly — Users trust recommendations they understand
- Don't repeat resume — If user just ran resume, don't re-print all the same info
GitHub 仓库
相关推荐技能
llamaguard
其他LlamaGuard是Meta推出的7-8B参数内容审核模型,专门用于过滤LLM的输入和输出内容。它能检测六大安全风险类别(暴力/仇恨、性内容、武器、违禁品、自残、犯罪计划),准确率达94-95%。开发者可通过HuggingFace、vLLM或Sagemaker快速部署,并能与NeMo Guardrails集成实现自动化安全防护。
cost-optimization
其他这个Claude Skill帮助开发者优化云成本,通过资源调整、标记策略和预留实例来降低AWS、Azure和GCP的开支。它适用于减少云支出、分析基础设施成本或实施成本治理策略的场景。关键功能包括提供成本可视化、资源规模调整指导和定价模型优化建议。
quantizing-models-bitsandbytes
其他这个Skill使用bitsandbytes库量化大语言模型,能在GPU内存有限时通过8位或4位量化减少50-75%内存占用,同时保持精度损失最小。它支持INT8、NF4、FP4等多种量化格式,可与HuggingFace Transformers无缝集成,适用于需要部署更大模型或加速推理的场景。还提供QLoRA训练和8位优化器支持,让开发者能轻松实现高效模型压缩。
dispatching-parallel-agents
其他该Skill用于并行处理3个以上无依赖关系的独立故障,可为每个问题域分派专属Claude代理同时执行调查修复。它通过并发处理多个独立问题显著提升故障排查效率,特别适用于测试文件、子系统等无共享状态的场景。
