スキル一覧に戻る

next-step

bitwize-music-studio
更新日 2 days ago
3 閲覧
209
37
209
GitHubで表示
その他general

について

この「次のステップ」スキルは、アルバムプロジェクトの状態を分析し、ユーザーが「次に何をすべきですか?」と尋ねた際に最適な単一の次のアクションを推奨します。セッションのコンテキストを確認するか、すべてのアルバムをスキャンすることでワークフローの位置を判断し、具体的なガイダンスを提供します。このスキルはワークフロー・ルーターとして機能し、Read、Glob、bitwize-music-mcpなどのツールを使用して進捗を評価し、次のステップを指示します。

クイックインストール

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-skills
Git クローン代替
git 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

  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

GitHub リポジトリ

bitwize-music-studio/claude-ai-music-skills
パス: skills/next-step
0
ai-musicai-music-toolsaudio-masteringclaudeclaude-codeclaude-code-plugin

関連スキル

llamaguard

その他

LlamaGuardは、暴力やヘイトスピーチなど6つの安全性カテゴリーにおいて、LLMの入力と出力をモデレートするMetaの70-80億パラメータモデルです。94〜95%の精度を提供し、vLLM、Hugging Face、Amazon SageMakerを使用してデプロイ可能です。このスキルを使用して、AIアプリケーションにコンテンツフィルタリングと安全策を簡単に統合できます。

スキルを見る

cost-optimization

その他

このClaudeスキルは、リソースの適正サイジング、タグ付け戦略、支出分析を通じて、開発者がクラウドコストを最適化することを支援します。AWS、Azure、GCPにわたるクラウド支出の削減とコストガバナンスの実施のためのフレームワークを提供します。インフラコストの分析、リソースの適正サイジング、または予算制約への対応が必要な際にご利用ください。

スキルを見る

quantizing-models-bitsandbytes

その他

このスキルは、bitsandbytesを使用してLLMを8ビットまたは4ビット精度に量子化し、精度の低下を最小限に抑えつつ50〜75%のメモリ削減を実現します。限られたGPUメモリでより大規模なモデルを実行したり、推論を高速化するのに理想的で、INT8、NF4、FP4などのフォーマットをサポートしています。HuggingFace Transformersと統合され、QLoRAトレーニングや8ビットオプティマイザーを可能にします。

スキルを見る

dispatching-parallel-agents

その他

このClaudeスキルは、複数のエージェントを配備し、3つ以上の独立した問題を並行して調査・修正します。共有状態や依存関係がなく解決可能な、無関係な障害が発生するシナリオ向けに設計されています。中核となる機能は並列問題解決であり、効率を最大化するために独立した問題領域ごとに1つのエージェントを割り当てます。

スキルを見る