From bitwize-music
Runs session startup for bitwize-music project: verifies MCP setup, loads config/state/overrides, handles plugin upgrades, reports album ideas/progress/status. Use at fresh session start.
npx claudepluginhub bitwize-music-studio/claude-ai-music-skills --plugin bitwize-musicThis skill is limited to using the following tools:
Run the full session start procedure and report project status to the user.
Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.
Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
Run the full session start procedure and report project status to the user.
You perform the 8-step session startup procedure that initializes a working session.
Quick dependency check:
~/.bitwize-music/venv/bin/python3 -c "import mcp" 2>&1 >/dev/null && echo "MCP ready" || echo "MCP missing"
/bitwize-music:setup mcp~/.bitwize-music/config.yaml doesn't exist): suggest /bitwize-music:configureRead ~/.bitwize-music/config.yaml.
If missing, tell user to run /bitwize-music:configure.
Read paths.overrides from config (default: {content_root}/overrides):
{overrides}/CLAUDE.md — incorporate instructions if found{overrides}/pronunciation-guide.md — note if foundRead ~/.bitwize-music/cache/state.json:
rebuild_state()
Compare plugin_version in state.json against current version in ${CLAUDE_PLUGIN_ROOT}/.claude-plugin/plugin.json:
plugin_version is null (first run or pre-upgrade-system): Set to current version, skip migrations${CLAUDE_PLUGIN_ROOT}/migrations/ for versions between stored and currentauto: Execute silently (run check first — skip if returns 0)action: Show description, ask user to confirm before executinginfo: Display to usermanual: Show instruction to userplugin_versionSkill model checking is no longer part of session start. Run /bitwize-music:skill-model-updater check manually when new Claude models are released.
Using data from state.json, report:
From state.ideas.counts — show count by status (Pending, In Progress, etc.)
Filter state.albums for status: "In Progress", "Research Complete", "Complete"
For each, show:
From state.albums — find tracks where sources_verified is "Pending"
If any found, warn: "These tracks have unverified sources — generation is blocked until verified."
From state.session:
Based on state, show ONE relevant tip:
| Condition | Tip |
|---|---|
| No albums exist | "Try /bitwize-music:tutorial to create your first album" |
| Ideas exist but no albums | "You have album ideas! Use /bitwize-music:album-ideas list to review them" |
| In-progress albums exist | "Resume where you left off: /bitwize-music:resume <album-name>" |
| Overrides loaded | "Custom overrides loaded from {overrides}/" |
| Overrides missing | "Customize your workflow with override files — see /reference/overrides/" |
| Pending verifications | "Source verification needed before generation can proceed" |
Also show one random general tip (rotate through these):
/bitwize-music:resume to quickly jump back into an album"/bitwize-music:clipboard to copy lyrics/prompts for Suno"/bitwize-music:mastering-engineer for professional results"End with: "What would you like to work on?"
SESSION START
=============
Setup: MCP ready, config loaded
Overrides: [loaded from {path} | not found (optional)]
State: [loaded | rebuilt | error]
ALBUM IDEAS
Pending: X | In Progress: Y
IN-PROGRESS ALBUMS
[album-name] (genre) - Status [X/Y tracks]
[album-name] (genre) - Status [X/Y tracks]
PENDING VERIFICATIONS
[album-name]: track-01, track-05
LAST SESSION
Album: [name] | Phase: [phase]
Pending: [actions]
TIP: [contextual tip]
What would you like to work on?