SKILL·FC25CF

next-step

bitwize-music-studio
Aktualisiert 1 month ago
10 Ansichten
358
81
358
Auf GitHub ansehen
Anderegeneral

Über

Die Next-Step-Fähigkeit analysiert Albumprojektzustände und empfiehlt die optimale nächste Einzelaktion, wenn Benutzer fragen: "Was soll ich als Nächstes tun?" Sie bestimmt die Workflow-Position durch Überprüfung des Sitzungskontexts oder Scannen aller Alben und liefert dann spezifische Anleitung. Diese Fähigkeit fungiert als Workflow-Router und nutzt Werkzeuge wie Read, Glob und bitwize-music-mcp, um den Fortschritt zu bewerten und nächste Schritte zu lenken.

Schnellinstallation

Claude Code

Empfohlen
Primär
npx skills add bitwize-music-studio/claude-ai-music-skills -a claude-code
Plugin-BefehlAlternativ
/plugin add https://github.com/bitwize-music-studio/claude-ai-music-skills
Git CloneAlternativ
git clone https://github.com/bitwize-music-studio/claude-ai-music-skills.git ~/.claude/skills/next-step

Kopieren Sie diesen Befehl und fügen Sie ihn in Claude Code ein, um diese Fähigkeit zu installieren

Dokumentation

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 Repository

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

Frequently asked questions

What is the next-step skill?

next-step is a Claude Skill by bitwize-music-studio. Skills package instructions and resources that Claude loads on demand, so Claude can perform next-step-related tasks without extra prompting.

How do I install next-step?

Use the install commands on this page: add next-step to Claude Code as a plugin, or clone its repository into your skills directory, then restart Claude so it picks up the skill.

What category does next-step belong to?

next-step is in the Other category, tagged general.

Is next-step free to use?

Yes. next-step is listed on AIMCP and free to install. It runs inside Claude, so no separate service account is required to use the skill itself.

Verwandte Skills

llamaguard
Andere

LlamaGuard ist Metas 7-8B-Parameter-Modell zur Moderation von LLM-Eingaben und -Ausgaben in sechs Sicherheitskategorien wie Gewalt und Hassrede. Es bietet eine Genauigkeit von 94-95 % und kann mit vLLM, Hugging Face oder Amazon SageMaker eingesetzt werden. Nutzen Sie diese Skill, um Inhaltsfilterung und Sicherheitsguardrails einfach in Ihre KI-Anwendungen zu integrieren.

Skill ansehen
cost-optimization
Andere

Diese Claude Skill unterstützt Entwickler bei der Optimierung von Cloud-Kosten durch Ressourcen-Dimensionierung, Tagging-Strategien und Ausgabenanalysen. Sie bietet einen Rahmen zur Senkung von Cloud-Ausgaben und zur Implementierung von Kosten-Governance für AWS, Azure und GCP. Nutzen Sie sie, wenn Sie Infrastrukturkosten analysieren, Ressourcen richtig dimensionieren oder Budgetvorgaben einhalten müssen.

Skill ansehen
sports-betting-analyzer
Andere

Diese Claude Skill analysiert Sportwettenmärkte inklusive Handicaps, Over/Unders und Spezialwetten, indem sie historische Trends und situative Statistiken untersucht, um Wertwetten zu identifizieren. Sie liefert strukturierte Markdown-Ausgaben mit umsetzbaren Empfehlungen zu Bildungszwecken. Entwickler sollten dies für Sportwetten-Analysetools nutzen, wobei zu beachten ist, dass es nur zur Unterhaltung/Bildung konzipiert wurde.

Skill ansehen
quantizing-models-bitsandbytes
Andere

Diese Fähigkeit quantisiert LLMs auf 8-Bit- oder 4-Bit-Präzision mittels bitsandbytes und erreicht dabei eine Speicherreduzierung von 50–75 % bei minimalem Genauigkeitsverlust. Sie ist ideal für den Betrieb größerer Modelle mit begrenztem GPU-Speicher oder zur Beschleunigung von Inferenzvorgängen und unterstützt Formate wie INT8, NF4 und FP4. Die Fähigkeit integriert sich in HuggingFace Transformers und ermöglicht QLoRA-Training sowie 8-Bit-Optimierer.

Skill ansehen