session-start

To initialize a fresh Claude session, run the session-start skill at the beginning of your work. It verifies your setup, loads config and state cache, checks skill models, and then reports your immediate project status, including pending verifications and last session context.

Before starting an automated Claude music-production workflow, you need MCP availability, a valid configuration file, and up-to-date skill models. The session-start process checks these dependencies automatically and can rebuild the state cache if needed to ensure readiness.

Yes, booting a new session allows you to check in-progress albums and pending verifications. The initialization process loads your state cache and reports current project status, summarizing album ideas, ongoing work, and the context of your last session.

Session initialization checks if skill models are up to date via the skill-model-updater check. If models are outdated, the process ensures they are updated to maintain system health before fully loading the project state and providing contextual workflow tips.

Claude workflow startup fails when loading state and config if MCP is unavailable, the configuration file is invalid, or skill models are missing. The session-start verification step identifies these issues, checks readiness, and can rebuild the state cache to resolve loading errors.

The best way to automate session startup for a new music-production project is to run the session-start skill. It applies at the start of a new project to verify setup, load config and state, check models, and provide contextual tips with recommended next actions.